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).

Source multiline grep with pcregrep

Terminal - Source multiline grep with pcregrep
pcregrep --color -M -N CRLF "owa_pattern\.\w+\W*\([^\)]*\)" source.sql
2010-11-11 12:53:40
User: hute37
0
Up
Down
Source multiline grep with pcregrep

grep multiline in Perl regexp syntax with pcregrep

Show sample output | Add to favourites | Report as malicious

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

without need to install grep variant pcregrep, you can do multiline search with grep.

grep -Pzo "(?s)^(\s*)\N*main.*?{.*?^\1}" *.c

Explain:

-P activate perl-regexp for grep (a powerful extension of regular extensions)

-z supress newline at the end of line, subtituting it for null character. That is, grep knows where end of line is, but see input as a big one line.

-o print only matching. Because using -z, all file is like a big line, so if there is a match, all file would be printed, this way it don't.

in regexp:

(?s) activate PCRE_DOTALL, which means that '.' find any character or newline

\N find anything except newline, even with PCRE_DOTALL activated

.*? find '.' in nongreedy mode, that is, stops as soon as possible.

^ find start of line

\1 backreference to first group (\s*) This is a try to find same indentation of method

As you can imagine, this print the main method in a C (*.c) source file.

Comment by unixmonkey24864 91 weeks and 2 days ago

grep version is very cool ;)

i like the trick to match closing brace with backreferences ...

Comment by hute37 91 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts