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

Save a file you edited in vim without the needed permissions

Terminal - Save a file you edited in vim without the needed permissions
:w !sudo tee %
2009-02-25 16:27:24
User: skinp
Functions: tee
636
Save a file you edited in vim without the needed permissions

I often forget to sudo before editing a file I don't have write permissions on. When you come to save that file and get the infamous "E212: Can't open file for writing", just issue that vim command in order to save the file without the need to save it to a temp file and then copy it back again.

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
:w !sudo tee > /dev/null %
2010-03-24 20:04:26
User: idemal
Functions: tee
Tags: vim sudo tee
26

Write a file you edited in Vim but that you do not have the permissions to write to (unless you use sudo.) Same as #1204 but without the echo to stdout that I find annoying.

command W :execute ':silent w !sudo tee % > /dev/null' | :edit!
2011-10-06 20:37:54
Functions: command tee
Tags: vim sudo tee
7

Calls sudo tee like all the other lines, but also automatically reloads the file.

Optionally you can add

command Wq :execute ':W' | :q

and

command WQ :Wq

to make quitting easier

:w !pfexec tee %
:%!sudo tee %
2011-06-17 07:16:23
User: antone
Functions: tee
Tags: vim sudo tee
1

probably just like 1204, but uses tee as a filter (+ I actually understand how this one works)

w !sudo cat >%

Know a better way?

If you can do better, submit your command here.

What others think

this is just awesome! of course you have to have sudo rights...

Comment by nottings 334 weeks and 6 days ago

awe-some !

Comment by pyrho 334 weeks and 6 days ago

Unfortunately this does not work well in gvim.

Comment by trey 334 weeks and 2 days ago

I wish I could vote this up more than once. Thanks!

Comment by Alanceil 334 weeks and 2 days ago

nice - thanks!

Comment by waltharius 332 weeks and 1 day ago

I use

:w !cat > %

which is similar, but shorter (you can add sudo in there if you want).

Comment by spatz 328 weeks and 2 days ago

awesome!

Comment by Iany 324 weeks and 4 days ago

I always quit vi and sudo vi when I find I haven't write permission before. This command save me much time.

Comment by kylexlau 323 weeks and 5 days ago

!sudo cat > % won't work:

* the su-ed command is "cat" but

* > % isn't an argument for "cat", but a redirection

it's the same for sudo echo > myRootFile.txt

you could try with sudo sh -c "cat > %" but it's longer

so tee is ok.

comments welcome.

Comment by ioggstream 315 weeks and 6 days ago

greatest commend ever!!! tnx!

Comment by ilyxa 312 weeks and 6 days ago

how often did i miss this command, perfect!

+1 vote for greatest command ever

Comment by buergi 307 weeks and 5 days ago

i have added:

cmap w!! %!sudo tee > /dev/null %

to my .vimrc, so I can just use :w!! to write files with sudo

Comment by f3lix 299 weeks ago

Pretty sweet. I'm an Emacs guy, but I'm impressed with the succinct way vi handles changing effective UID.

By the way, does this work for files that have spaces in the filenames? I would guess that it wouldn't. Is it fixable by double-quoting the %?

Comment by hackerb9 295 weeks and 5 days ago

You made me curious about filenames with spaces so I had to try it out. It only works with the "%". But as a general rule, I try not to name Unix files with spaces.

Comment by skinp 295 weeks and 5 days ago

Really nice! I just freaked out when I tried this with nvi (in Ubuntu 9.10)... it did not ask for my password and yet it wrote an /etc file. Please shed some light!

Comment by ez77 291 weeks and 5 days ago

Wow, this will come in handy. So will f3lix's :w!!

but I like to use abbreviations, i think they are cleaner than remapping:

ca w!! w !sudo tee "%"
Comment by jearsh 286 weeks and 5 days ago

Thanks for this. It will save me a lot of frustration.

Comment by idemal 278 weeks and 5 days ago

is this also possible for nano?

Comment by rubo77 269 weeks ago

Cool.!

Comment by knityster 256 weeks and 1 day ago

Make sure to configure sudo properly to ask you for your ROOT password and not your USER password.

Otherwise it reduces the security of your system.

Comment by grep 234 weeks and 1 day ago

:w !sudo tee %

I'm hoping someone can elaborate on this command for me.

Not sure I understand what the "%" is doing, and where tee is getting its input from. Tee reads from standard input and outputs to the first argument (file), which in this case, is the "%". In VIM, the "%" is often used with regular expressions to mean "every line in the file".

So how is this working? Because using those definitions, the command doesn't make any sense.

Comment by yohhan 230 weeks and 5 days ago

...I should add, great command. This situation happens to me all of the time.

Comment by yohhan 230 weeks and 5 days ago

Have my babies? Just kidding. Awesome solution for a common derp.

Comment by SpaceKraken 229 weeks and 2 days ago

I can not tell you how often i use this.

Comment by threv 189 weeks and 5 days ago

@yohhan % in vim command line mode , It represents current file, you can test it with :!echo % in vim

Comment by dfang 156 weeks and 1 day ago

@yohhan or :h cmdline-special

Comment by dfang 156 weeks and 1 day ago

Your point of view

You must be signed in to comment.