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:
POSIX requires this "string truncating" functionality.
might as well use it, at least for very small tasks where invoking sed and using RE is overkill.
There is 1 alternative - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
You need to quote "$a" in the echo or it'll drop multiple spaces from the input. e.g.
echo "a b"|se aa b
splante: thank you.
i have also used this one-liner as a simple way to transform tabs to spaces,
e.g., where output from a program wraps on the terminal solely because it uses tabs, making it more difficult to read.
fstat | se pattern
if we quote the "$a" variable then of course we'll get the tabs.
but in other situations quoting "$a" is useful. e.g. to prevent the shell from expanding certain characters. imagine if some program is listening on an internet socket, and you do
netstat | se LIS
you might not like what you get for the output, unless you have put quotes around "$a".
it seems this website might also benefit from some added attention to shell quoting: i can only see one space between a and b in your example.