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:
There are 4 alternatives - vote for the best!
Uses shell expansion to create a back-up called file.txt.bak
Remember to backup everything before changing it so you can restore all to normal.
less symbols, tab completion.
including # export SIMPLE_BACKUP_SUFFIX="_`date +%F`" in your .bashrc provides you to easily timestamp your files
If you can do better, submit your command here.
You must be signed in to comment.
this is using the bash shell I think...
The same thing will work using mv e.g.
mv filename{,.bak}nice command
I cannot tell you how many types I've typed out this command the hard way.
Of course one could write a bash/perl one-liner that would do the same thing "backify, or somesuch" with less typing :-D
Here is some info on the general case.
http://www.linuxjournal.com/content/bash-brace-expansion
Using tab-completion, I don't know how much time this would save, especially having to type out all the symbols
Lots of time. Typing symbols is not difficult. Think of a dir with files named test1_a2_tt.dat or something, but hundreds of them, tab completion will only help so much here.
Or think of a case when you are not in the directory, but want to backup/edit the file from where you are.
I prefer tab completion too, i.e. start typing the filename again and then tab, adding .bak to the end.
Okay, I get it now. There can't be a space between filename and the opening brace. For anyone more newb than me... NO SPACES!
tab completion or middle-click can be faster, that depends. anyway the game is to find the best solution in each case :P
Another option would be to do [CTRL-W] to cut the filename, then [CTRL-Y][space][CTRL-Y].bak. If there are non-keyword characters (ie [[:alnum:]_] in the , you'll have to hit CTRL-W a few times consecutively.
Very handy when tab-complete does not work, and no mouse working from console :)
It's very useful~
you can use : mv, diff, ...