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.


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

Psst. Open beta.

Wow, didn't really expect you to read this far down. The latest iteration of the site is in open beta. It's a gentle open beta-- not in prime-time just yet. It's being hosted over at UpGuard (link) and you are more than welcome to give it a shot. Couple things:

  • » The open beta is running a copy of the database that will not carry over to the final version. Don't post anything you don't mind losing.
  • » If you wish to use your user account, you will probably need to reset your password.
Your feedback is appreciated via the form on the beta page. Thanks! -Jon & CLFU Team

Remote screenshot

Terminal - Remote screenshot
DISPLAY=":0.0" import -window root screenshot.png
2010-02-17 13:02:24
User: walterl
18
Remote screenshot

The `export` is unnecessary if it's only applicable to the one command.

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
DISPLAY=:0.0 import -window root /tmp/shot.png
2010-10-28 12:00:00
User: depesz
25

Of course it requires import command, from imagemagick tools, but it's simpler to type, and imagemagick is usefull anyway.

ssh [email protected] "DISPLAY=:0.0 import -window root -format png -"|display -format png -
2011-04-08 01:07:41
User: splante
Functions: ssh
12

Admittedly, I'd never have thought of this without the earlier examples, but here's one that you can execute from your workstation to just display the image from another, without separately doing a file transfer, etc. By the way, I hear a loud beep coming from the other room, so I guess it's not too stealthy :-D

DISPLAY=":0.0"; export DISPLAY; import -window root gotya.png
2010-02-17 09:13:54
User: Abiden
Functions: export
3

Say if you're logged into a remote system via ssh and this system has an x window system, but yet you still want a screen shot of what's going on graphically. This will do it for you. :-)

export DISPLAY=":0.0" && import -window root screenshot.png
2010-02-17 12:13:49
User: fraktil
Functions: export
-3

Like the given command, but combines _DISPLAY=":0.0"_ with _export DISPLAY_ to get _export DISPLAY=":0.0"_ and only imports if DISPLAY is set successfully.

Know a better way?

If you can do better, submit your command here.

What others think

Thanks for this!

I've tried, and seemed to work although my question now is how can I deactivate screensaver/power saving when taking the screenshot, because all I'm getting is a black screenshot.

Thanks :)

Comment by inkel 331 weeks and 2 days ago

@inkel Besides something like

kill $(ps ax | grep screensaver | grep -v grep | awk '{ print $1 }')

I usually just use x11vnc to make the current X session VNC accessible and disable the screensaver via VNC.

Comment by walterl 331 weeks and 2 days ago

Your point of view

You must be signed in to comment.