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

Better way to use notify-send with at or cron

Terminal - Better way to use notify-send with at or cron
DISPLAY=:0.0 XAUTHORITY=~/.Xauthority notify-send test
2010-08-03 01:17:02
User: aurium
11
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

Alternatives

There is 1 alternative - 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: adeverteuil
Functions: at echo
Tags: notify-send
20

You can write a script that does this :

remind <minutes> [<message>]
echo notify-send test | at now+1minute
2010-08-08 03:11:11
User: polar
Functions: at echo test
Tags: notify-send
4

The simplest way to do it.

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

Know a better way?

If you can do better, submit your command here.

What others think

Thanks aurium, I'd also suggest using a ?here string? for even better clarity than piping with echo :

at now+1minute <<< "DISPLAY=:0.0 XAUTHORITY=~/.Xauthority notify-send test"
Comment by adeverteuil 315 weeks and 2 days ago

Also, so you don't miss the reminder you may want to use --urgency=critical

Comment by bostonvaulter 313 weeks and 2 days ago

KDE users, in order to send a event to your KDE notifier you can use the following:

kdialog --passivepopup "breakfast ready!"
Comment by grinob 98 weeks and 4 days ago

Your point of view

You must be signed in to comment.