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.

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:



2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.

Top Tags



quit gvim remotely

Terminal - quit gvim remotely
gvim --remote-send ":q!<CR>"
2012-04-25 12:01:57
User: kev
quit gvim remotely


There are 3 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

How do you specify which gvim session you're sending the command to? Does this broadcast ":q!" to all processes running gvim?

Comment by bartonski 155 weeks and 5 days ago


If you have multiple gvim instances.

`C:\> gvim --serverlist`

`C:\> gvim --servername GVIM2 --remote-send ":q!"`

Comment by kev 155 weeks and 5 days ago
C:\> gvim --serverlist C:\> gvim --servername GVIM2 --remote-send ":q!"
Comment by kev 155 weeks and 5 days ago

Very useful, but how to pick the right server name between GVIM41 and GVIM18?

I've extended the suggestion of Kev by creating an executable script to be launched in place of gvim:

gvim --servername `basename $1` $1

The ideal would be to call it "gvim", put it in the path and use it to open files. This will make a lot easier to open the right server:

gvim --servername .BASHRC [...]
Comment by ntropia 155 weeks and 4 days ago

Your point of view

You must be signed in to comment.