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/
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.
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
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:
If you have a bunch of small files that you want to cat to read, you can cat each alone (boring); do a cat *, and you won't see what line is for what file, or do a grep . *. "." will match any string and grep in multifile mode will place a $filename: before each matched line. It works recursively too!!
There are 2 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
Unfortunately '.' doesn't match empty lines. '^' does match everything
This is a good idea. The empty lines thing occurred to me too, but in the cases I'm thinking of you probably aren't interested in the empty lines anyway. If there happens to be only one file in the dir, you don't get the filename, so you probably won't want to use this technique in a script, but it's handy for just typing in.
this is a kind of command-line trick I use to read splitted config files. so no I'm not interested on blanks and it is not intended for scripting :) . But I like the "including blank lines" variant, because looks geekier when I type it on the console :D
The "grep . *" command is super-cool but guys the "grep ^ *" is pure awesomeness! thanks to both of you men @theist @unixmonkey8119