Hide

What's this?

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/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

OpenID
or
Sign in Register

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

World cup college
Hide

Stay in the loop…

Follow the Tweets.

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

Subscribe to the feeds.

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:

Hide

News

2010-03-03 - Commandlinefu @ SXSW 2010
Am going to be at SXSW this year, in case you want to submit any CLI nuggets or suggestions to me in person. Ping me on the @codeinthehole Twitter account.
2009-09-12 - Email updates now available
You can now enable email updates to let you know each time you're command is commented on.
2009-07-11 - API and javascript blog widget now available
A simple API has been released, allowing commands to be retrieved in various formats. This also allows commands to be embedded on blogs/homepages.
2009-05-17 - Added duplicate suggestions to the new command form
When adding a new command, a quick background search is performed to make sure you're not duplicating a command already in the system.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

quickly backup or copy a file with bash

Terminal - quickly backup or copy a file with bash
cp filename{,.bak}
2009-02-05 17:12:03
User: elofland
Functions: cp
172
Up
Down
quickly backup or copy a file with bash
Add to favourites | Report as malicious

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
cp -bfS.bak filename filename
2009-06-30 14:17:28
User: ioggstream
Functions: cp
4
Up
Down
quickly backup or copy a file with bash

less symbols, tab completion.

including # export SIMPLE_BACKUP_SUFFIX="_`date +%F`" in your .bashrc provides you to easily timestamp your files

Comments (0) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

this is using the bash shell I think...

The same thing will work using mv e.g.

mv filename{,.bak}

nice command

Comment by finkployd 57 weeks and 1 day ago

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

Comment by QuantumFTL 57 weeks ago

Here is some info on the general case.

http://www.linuxjournal.com/content/bash-brace-expansion

Comment by terrasect 57 weeks ago

Using tab-completion, I don't know how much time this would save, especially having to type out all the symbols

Comment by swegner 55 weeks and 4 days ago

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.

Comment by jonathan 55 weeks and 2 days ago

Or think of a case when you are not in the directory, but want to backup/edit the file from where you are.

Comment by ozymandias 54 weeks and 3 days ago

I prefer tab completion too, i.e. start typing the filename again and then tab, adding .bak to the end.

Comment by Buzzcp 47 weeks and 5 days ago

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!

Comment by xizdaqrian 45 weeks and 2 days ago

tab completion or middle-click can be faster, that depends. anyway the game is to find the best solution in each case :P

Comment by ioggstream 35 weeks and 4 days ago

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.

Comment by intuited 11 weeks and 3 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts