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.

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.

UpGuard checks and validates configurations for every major OS, network device, and cloud provider.

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:



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!

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 is 1 alternative - 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 312 weeks and 3 days ago


If you have multiple gvim instances.

`C:\> gvim --serverlist`

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

Comment by kev 312 weeks and 3 days ago
C:\> gvim --serverlist C:\> gvim --servername GVIM2 --remote-send ":q!"
Comment by kev 312 weeks and 3 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 312 weeks and 2 days ago

Your point of view

You must be signed in to comment.