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.

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

Commands tagged parsing from sorted by
Terminal - Commands tagged parsing - 4 results
sh -c 'url="http://youtu.be/MejbOFk7H6c"; vid="`for i in ".*youtu\.be/\([^\/&?#]\+\)" ".*youtu.\+v[=/]\([^\/&?#]\+\)" ".*youtu.\+embed/\([^\/&?#]\+\)"; do expr "${url}" : "${i}"; done`"; if [ -n "${vid}" ]; then echo ${vid}; else echo "${url}"; fi'
2013-09-04 19:33:09
User: qwertyroot
Functions: echo sh
2

url can be like any one of followings:

url="MejbOFk7H6c" url="http://youtu.be/MejbOFk7H6c" url="https://youtube.com/watch?feature=player_embedded&v=MejbOFk7H6c#t" url="//www.youtube.com/v/MejbOFk7H6c?hl=ru_RU&version=3&rel=0" url="http://www.youtube.com/embed/MejbOFk7H6c?feature=player_embedded"

If url mismatching, whole url will be returned.

Opening_tag((?:(?!Unwanted_tag).)*)Closing_tag
2012-02-28 02:54:57
User: DewiMorgan
Tags: regex parsing
0

Sometimes, especially when parsing HTML, you want "all text between two tags, that doesn't contain another tag".

For example, to grab only the contents of the innermost <div>s, something like:

/<div\b[^>]*>((?:(?!<div).)*)</div>/

...may be your best option to capture that text.

It's not always needed, but is a powerful arrow in your regex quiver in those cases when you do need it.

Note that, in general, regular expressions are the Wrong Choice for parsing HTML, anyway. Better approaches are solutions which let you navigate the HTML as a proper DOM. But sometimes, you just need to use the tools available to you. If you don't, then you have two problems.

mech-dump --links --absolute http://www.commandlinefu.com
2011-11-19 03:40:52
User: sputnick
Tags: perl html parsing
2

You need to install WWW::Mechanize Perl module with

# cpan -i WWW::Mezchanize

or by searching mechanize | grep perl in your package manager

With this command, you can get forms, images, headers too

vim -n -es -c 'g/# CommandParse/+2,/^\s\+esac/-1 d p | % d | put p | %<' -c 'g/^\([-+]\+[^)]\+\))/,/^\(\s\+[^- \t#]\|^$\)/-1 p' -c 'q!' $0
2009-12-19 08:32:00
User: syladmin
Functions: vim
0

A really fun vim oneliner for auto documenting your option's parsing in your script.

# print the text embeded in the case that parse options from command line.

# the block is matched with the marker 'CommandParse' in comment, until 'esac'

extract_cmdl_options()

{

# use vim for parsing:

# 1st grep the case block and copy in register @p + unindent in the buffer of the file itself

# 2nd filter lines which start with --opt or +opt and keep comment on hte following lines until an empty line

# 3rd discard changes in the buffer and quit

vim -n -es -c 'g/# CommandParse/+2,/^\s\+esac/-1 d p | % d | put p | %

-c 'g/^\([-+]\+[^)]\+\))/,/^\(\s\+[^- \t#]\|^$\)/-1 p' \

-c 'q!' $0

}

example code:http://snipplr.com/view/25059/display-embeded-comments-for-every-opt-usefull-for-auto-documenting-your-script/