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.

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

Universal configuration monitoring and system of record for IT.
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

May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!
Hide

Top Tags

Hide

Functions

Hide

Credits

Open (in vim) all modified files in a git repository

Terminal - Open (in vim) all modified files in a git repository
vim `git status | grep modified | awk '{print $3}'`
2012-11-19 09:48:46
User: TetsuyO
Functions: awk grep vim
0
Open (in vim) all modified files in a git repository

This oneliner gets all the 'modified' files in your git repository, and opens all of them in vim.

Very handy when you're starting to work in the morning and you simply want to review your modified files before committing them.

Maybe there are better ways to do that (and maybe integrated in vim and/or git, who knows), but I found quicker to do this oneliner.

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
vim `git status --porcelain | sed -ne 's/^ M //p'`
2012-11-21 06:31:46
User: seb1245
Functions: sed vim
Tags: vim git
5

The option --porcelain makes the output of git easier to parse.

This one-liner may not work if there is a space in the modified file name.

vim `git diff --name-only`
2015-02-25 11:12:49
User: mbudde
Functions: diff vim
Tags: vim git
1

For editing files added to the index:

vim `git diff --name-only --cached`

To edit all changed files:

vim `git diff --name-only HEAD`

To edit changed files matching glob:

vim `git diff --name-only -- '*.html'`

If the commands needs to support filenames with whitespace, it gets a bit hacky (see http://superuser.com/questions/336016/invoking-vi-through-find-xargs-breaks-my-terminal-why for the reason):

git diff --name-only -z | xargs -0 bash -c '</dev/tty vim "$@"' x

The last part can be put in a script named e.g. vimargs, and used with any command outputting NUL separated filenames:

git grep -lz foobar | vimargs
vim -p `git --porcelain | awk {print $2}`
2013-04-29 21:52:23
User: cnelsonsic
Functions: awk vim
Tags: vim git
0

Opens all files in the index (modified plus not added yet) in tabs in vim.

git status --porcelain | sed -ne 's/^ M //p' | tr '\n' '\0' | tr -d '"' | xargs -0 vim
2014-05-08 08:36:27
User: uschrisf
Functions: sed tr xargs
Tags: vim git
0

Works even with spaces in filenames.

As an alias in .gitconfig:

[alias]

editchanged = "!git status --porcelain | sed -ne 's/^ M //p' | tr '\\n' '\\0' | tr -d '\"' | xargs -0 vim"

Know a better way?

If you can do better, submit your command here.

What others think

You don't even need grep, awk can search too:

git status | awk '/modified/{ print $3 }'
Comment by flatcap 145 weeks ago

It is more robust to parse the "M" flag than the "modified" keyword from the output of git, because the command won't be confuzed when an unmodified file has the substring "modified" in its name

Comment by seb1245 144 weeks and 5 days ago

Your point of view

You must be signed in to comment.