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.

OpenID
or
Sign in Register

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

Hide

Credits

Site by David Winterbottom (user root).

I finally found out how to use notify-send with at or cron

Terminal - I finally found out how to use notify-send with at or cron
echo notify-send test | at now+1minute
2010-08-08 03:11:11
User: polar
Functions: at echo test
3
Up
Down
I finally found out how to use notify-send with at or cron

The simplest way to do it.

Works for me, at least. (Why are the variables being set?)

Add to favourites | Report as malicious

Alternatives

There are 2 alternatives - vote for the best!

Terminal - Alternatives
echo "export DISPLAY=:0; export XAUTHORITY=~/.Xauthority; notify-send test" | at now+1minute
2010-07-27 00:10:08
User: claudelepoisson
Functions: at echo
Tags: notify-send
19
Up
Down
I finally found out how to use notify-send with at or cron

You can write a script that does this :

remind <minutes> [<message>]
Comments (2) | Add to favourites | Report as malicious
DISPLAY=:0.0 XAUTHORITY=~/.Xauthority notify-send test
2010-08-03 01:17:02
User: aurium
Tags: notify-send
8
Up
Down
Better way to use notify-send with at or cron

we don't need to export variables to set a env to a command, we may do this before the command directly

Comments (2) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

when you run a command from an xterm or other terminal emulator within an X windows session you get access to certain environment variables (like $DISPLAY).

When things are run by cron or by an "actual terminal" (that comes up when you do ctr-alt-f1 on linux for example -- ctrl-alt-f7 to get back to X) then these environment variables aren't set.

Comment by infinull 149 weeks and 3 days ago

I see. Is there any way I can delete that submission, now?

Comment by polar 149 weeks and 3 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts