Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

OpenID
or
Sign in Register

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Extract raw URLs from a file

Terminal - Extract raw URLs from a file
egrep -ie "<*HREF=(.*?)>" index.html | awk -F\" '{print $2}' | grep ://
2009-02-05 17:51:14
User: wwest4
Functions: awk egrep grep
-1
Up
Down
Extract raw URLs from a file
Add to favourites | Report as malicious

Alternatives

There are 3 alternatives - vote for the best!

Terminal - Alternatives
egrep -ie "<*HREF=(.*?)>" index.html | cut -d "\"" -f 2 | grep ://
2011-03-29 18:20:50
User: fanfani
Functions: cut egrep grep
3
Up
Down
Extract raw URLs from a file

you can also use cut instead of awk. less powerful but probably faster. ;)

Comments (2) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

This fails if the HREF attribute of the anchor tag used a single-quote instead of a double quote. It also fails if the HREF attribute isn't the first attribute of the tag, or if there are two spaces (or a newline) between the tag and the attribute, and so on. It also can be done much more efficiently with a single command e.g.

perl -ne 'print "$1\n" if m,+]href=["'\''](\w+://[^"'\'']+),i' index.html
Comment by Rhomboid 224 weeks and 1 day ago

sigh, and of course this crappy site mangled the command because it contained angle brackets.

Comment by Rhomboid 224 weeks and 1 day ago

ok, and i guess it would be easy enough to fix the regex to match the RFC, if necessary... aside from saying that efficiency doesn't really matter here, i can't really argue that perl is better suited to the task... you should post your soln if you can figure out how.

Comment by wwest4 224 weeks and 1 day ago

er... can't really argue AGAINST perl being better suited.

Comment by wwest4 224 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts