{"id":10906,"date":"2025-06-16T02:00:00","date_gmt":"2025-06-16T06:00:00","guid":{"rendered":"https:\/\/www.both.org\/?p=10906"},"modified":"2025-06-10T11:14:46","modified_gmt":"2025-06-10T15:14:46","slug":"i-need-a-list-of-urls","status":"publish","type":"post","link":"https:\/\/www.both.org\/?p=10906","title":{"rendered":"I need a list of URLs"},"content":{"rendered":"
\r\n
\r\n \r\n <\/i>\r\n <\/a>\r\n <\/span>\r\n<\/div><\/div>\n

I teach a few university courses, and a former student recently emailed me to ask if she could get a copy of all the links from our “course links” page. She forgot to save the links during the Spring semester, and now that the course has ended, she can’t access the course to get to the links.<\/p>\n\n\n\n

My course had a lot of online readings, so this was not a small request. Fortunately, I was able to solve it by typing a few Unix commands. Here’s how I did it:<\/p>\n\n\n\n

Break up the text into words<\/h2>\n\n\n\n

The first step was pretty easy: save a copy of the “course links” page as an HTML file, in a temporary file I saved as \/tmp\/f<\/code>. This gave me the content for the page, which included weekly reminders, topic overviews, and links to online resources (the “weekly readings”).<\/p>\n\n\n\n

I only wanted to get a list of the URLs in this page. In HTML, each link is contained in the <a><\/code> “anchor” tag, with a hyper reference, so the link actually looks like:<\/p>\n\n\n\n

<a href=\"https:\/\/example.com\/\">link text<\/a><\/code><\/pre>\n\n\n\n
Our course links were a bit more complicated, because Canvas adds some other information to links, so each link actually looked like:<\/p>\n\n\n\n
<a class=\"inline_disabled\" href=\"https:\/\/example.com\/\" target=\"_blank\" rel=\"noopener\">link text<\/a><\/code><\/pre>\n\n\n\n
I only needed the href<\/code> part for each <a><\/code> tag, because that has the URL for each link. One way to do this would be to process the HTML with a one-off program to print just the tags (anything that starts with <<\/code> and ends with ><\/code>). But I realized there was an easier way: break up the text into words by turning each space character into a newline character. Then I would have each “word” on a line by itself. More importantly, each link would become a series of separate lines, like this:<\/p>\n\n\n\n
<a\nclass=\"inline_disabled\"\nhref=\"https:\/\/example.com\/\"\ntarget=\"_blank\"\nrel=\"noopener\">link\ntext<\/a><\/code><\/pre>\n\n\n\n
This task calls for the tr<\/strong> command, which translates<\/em> one character into another character:<\/p>\n\n\n\n
$ tr ' ' '\\n' < \/tmp\/f<\/code><\/pre>\n\n\n\n
Find the links<\/h2>\n\n\n\n
With every word from the HTML file on a separate line, I can search for any line that starts with href=<\/code>. These should be the URLs for each link in the page. In theory, this might catch some other text in the file, but it’s unlikely because I wrote the page and I know<\/em> I don’t have any other text that would contain href=<\/code>.<\/p>\n\n\n\n
The grep<\/strong> command is made for this task. This will search its input and only print lines that match a pattern, which could be a simple string. For example, this will print all lines that have href=<\/code> at the start of a line:<\/p>\n\n\n\n
$ tr ' ' '\\n' < \/tmp\/f | grep '^href='<\/code><\/pre>\n\n\n\n
However, that will return lines that contain not just the URL, but the href=<\/code> and quotes around the URL. That means each URL will be printed like this:<\/p>\n\n\n\n
href=\"https:\/\/example.com\/\"\n<\/code><\/pre>\n\n\n\n
I wanted the list to look nice for my former student, which meant I wanted to remove the unneeded text.<\/p>\n\n\n\n
The awk<\/strong> command is a simple but flexible scripting language that makes it easy to pull apart a line into fields<\/em> that you can act upon. Normally, the field separator<\/em> is any kind of white space, like a tab or space character. But you can also specify your own field separator with the -F<\/code> option.<\/p>\n\n\n\n
If I assume the quote mark is a field separator, then the three fields are: href=<\/code> and https:\/\/example.com\/<\/code> and an empty field at the end.<\/p>\n\n\n\n
That was my solution: for any line that starts with https=<\/code>, use the quote mark as the field separator, and print the second field:<\/p>\n\n\n\n
$ tr ' ' '\\n' < \/tmp\/f | awk -F\\\" '\/^href=\/ {print $2}'<\/code><\/pre>\n\n\n\n
Print only unique URLs<\/h2>\n\n\n\n
To make the list easy to read, I decided to sort the output for my student. To do that, you can use the sort<\/strong> command, which does as the name suggests:<\/p>\n\n\n\n
$ tr ' ' '\\n' < \/tmp\/f | awk -F\\\" '\/^href=\/ {print $2}' | sort<\/code><\/pre>\n\n\n\n
This also identified another issue: sometimes, I listed the same link in different weeks on the “course links” page. I wanted to make the list as short as possible, which meant I only wanted to print one instance<\/em> of each unique link. The last step was to pass the output through the uniq<\/strong> command, which examines a sorted list and omits repeated lines, giving a list of unique lines:<\/p>\n\n\n\n
$ tr ' ' '\\n' < \/tmp\/f | awk -F\\\" '\/^href=\/ {print $2}' | sort | uniq<\/code><\/pre>\n\n\n\n
This gave the list of URLs that I could share with my former student. This was quite a long list, but as I said at the beginning: my course had a lot of online readings<\/em>. We can see the list has 65 URLs by adding the wc<\/strong> command, which counts characters, words, and lines .. but we can print only the line count with the -l<\/code> option:<\/p>\n\n\n\n
$ tr ' ' '\\n' < \/tmp\/f | awk -F\\\" '\/^href=\/ {print $2}' | sort | uniq | wc -l\n65<\/code><\/pre>\n\n\n\n
Just a few commands<\/h2>\n\n\n\n
This task is a tough one if you try to do it the “manual” way, by reading through the page, then right-clicking on each link, selecting “Copy” from the pop-up menu, and pasting that URL into an email. For 65 links, that’s going to take a long time. Let’s make the math easy and say it takes ten seconds to find a link<\/em>, evaluate if I’ve copied the link before, then copy<\/em> and paste<\/em> the link into an email. That’s 650 seconds to copy all of the links on the page, or over ten minutes.<\/p>\n\n\n\n
But by starting with the tenet that everything should be in an open format<\/a> like HTML, and embracing the command line<\/a> by typing a few standard Unix commands, this becomes an easy task: tr<\/strong> splits lines into words, which I can then process with awk<\/strong> to print URLs, then sort them with sort<\/strong>, and strip out repeats with uniq<\/strong>. I used the command line to do in seconds<\/em> what would have needed more than ten minutes to do by hand.<\/p>\n","protected":false},"excerpt":{"rendered":"
I used the command line to do in seconds what would have needed more than ten minutes to do by hand.<\/p>\n","protected":false},"author":33,"featured_media":3293,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[100,5],"tags":[104,91],"class_list":["post-10906","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-command-line","category-linux","tag-command-line","tag-linux"],"modified_by":"Jim Hall","_links":{"self":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/10906","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/users\/33"}],"replies":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=10906"}],"version-history":[{"count":1,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/10906\/revisions"}],"predecessor-version":[{"id":10907,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/10906\/revisions\/10907"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/media\/3293"}],"wp:attachment":[{"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=10906"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=10906"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=10906"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}