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.
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:
Same as previous but without fugly sed =x
This version now adds a header with consecutive numbering.
Fast and excludes words with apostrophes. For ubuntu, you can use wamerican or wbritish dictionaries, installable through aptitude.
if you want to replace "foo" with "bar" in all files in a folder, and put the resulting files into a new subfolder
Using large wordlists is cumbersome. Using password cracking programs with rules such as Hashcat or John the ripper is much more effective. In order to do this many times we need to "clean" a wordlist removing all numbers, special characters, spaces, whitespace and other garbage. This command will covert a entire wordlist to all lowercase with no garbage.
Join all sequentially named files in the directory.
Use this for files split by utilities like hjsplit and similar.
This command does not do/perform _any_ sanity checks before acting, except that it won't run unless there is a file that matches "*.001".
- The outfile should not already exist.
- There should be more than one file. (*.002 should exist as well as *.001)
- The file-count should match the number in the name of the last file in the series.
- None of the files should be empty.
- All files should be the same size, except for the last, which should usually be smaller, but never larger than the rest.
A safer altenative can be found here: http://pastebin.com/KSS0zU2F
The first grep rejects capitalised words since the dict has proper nouns in it that you mightn't want to use. The second grep rejects words with ending in apostrophe s, and the third forces the words to be at least 15 characters long.
this command example converts to 25 fps subtitles that were originally created for 24 fps movie
I liked vaporub's suggestion, here a little simplification of the sed command.
Multi-word parameters in my.cnf can be written with either hyphens or underscores. innodb_file_per_table is the same as innodb-file-per-table, as well as innodb_file-per_table. The script normalizes the parameter names to using underscores only, keeping from changing values (e.g. ?mysql-bin? parameter value should not change).
"normalize" a my.cnf file.
Another way of do it in debian like distros, don't know if works for others
This command should be the first file-editing command for a newbie. It clears file.txt (cat), and asks for input until EOF is entered on its own line (not written to file.txt).
No need for the ls -r and a sort is also not really needed.