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.

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

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.
Hide

Tags

Hide

Functions

vim read stdin

Terminal - vim read stdin
ls | vim +'set bt=nowrite' -
2011-12-24 07:33:49
User: kev
Functions: ls vim
5
vim read stdin

Alternatives

There are 5 alternatives - vote for the best!

Terminal - Alternatives
ls | view -
2012-01-04 07:18:44
User: lefada
Functions: ls
Tags: vim
0

view does not enable the buffer because it opens in read-only, so it does the same

Know a better way?

If you can do better, submit your command here.

What others think

Why set bt=nowrite?

Comment by Fudo 140 weeks and 1 day ago

@Fudo It just means the buffer won't be written to disk, and it's not strictly necessary. The dash is the main thing. This works too:

ls | vim -

If it were in an alias or something the nowrite is handy, but I don't know if it'd be worth typing out to save the disk access. Or is there a more important reason to use it, Unixmonkey?

Comment by splante 138 weeks and 4 days ago

Or:

ls | view -

Which will give you a RO view (and you can write the buffer at your leisure)

Comment by phlyingpenguin 137 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts