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:
At the start of a vi session and *before* saving any changes use ":!cp % %-" to make a backup of the current file being edited.
example: vi /data/some/long/path/file
:!cp% %-
creates /data/some/long/path/file-
There are 10 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
You do realize that vim can be set to backup files, right? Aside from that, you should check out the -b option for cp.
@jmcantrell command-line fu is about commands not config files.
In any case, I have been using "!cp % %-" since 1990 (when vim did not exist) and I prefer to name the backup file to my own convention. For me, "file" and "file-" is sufficient. However, this technique could also be used to make snapshots of the file as the edit progresses: "!cp % %-1! "!cp % %-2! "!cp % $-with-function-y" etc etc
:w! >> file
This may actually be a good way to create live patches of ascii files. Thanks for the idea.