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:
Copying and pasting from Office documents open in Office:mac can dirty your files with Windows CRLF and (inexplicably) Classic Mac OS LF newlines, which can break some tools. This snippet replaces them with good ol' Unix LF newlines.
Handle any bad named file which contains ",',\n,\b,\t,` etc
Store the file name as null character separated list
find . -print0 >name.lst
and retrieve it using
read -r -d ""
Eg:
find . -print0 >name.lst;
cat name.lst| while IFS="" read -r -d "" file;
do
ls -l "$file";
done
Let -p do it's voodoo and do absolutely nothing but set the output record separator :-)
awk version of 7210. Slightly longer, but expanding it to catch blank lines is easier:
awk 'BEGIN{RS="\0"}{gsub(/\n+/,"<SOMETEXT>");print}' file.txt
In case the line you want to join start with a char different than ", you may use \n.*"\n as regex.
----
this line ends here
but must be concatenated with this one
"this line ends here"
and should NOT be concatenated with this one
When you use a "for" construct, it cycles on every word. If you want to cycle on a line-by-line basis (and, well, you can't use xargs -n1 :D), you can set the IFS variable to .
wraps text lines at the specified width (90 here).
-s option is to force to wrap on blank characters
-b count bytes instead of columns