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.

World cup college
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

2010-03-18 - Top 10 commands explained
There's a great article by Peteris Krumins explaining the current top 10 commands: http://www.catonmat.net/blog/top-ten-one-liners-from-commandlinefu-explained/
2010-03-03 - Commandlinefu @ SXSW 2010
Am going to be at SXSW this year, in case you want to submit any CLI nuggets or suggestions to me in person. Ping me on the @codeinthehole Twitter account.
2009-09-12 - Email updates now available
You can now enable email updates to let you know each time you're command is commented on.
2009-07-11 - API and javascript blog widget now available
A simple API has been released, allowing commands to be retrieved in various formats. This also allows commands to be embedded on blogs/homepages.
Hide

Tags

Hide

Functions

Update twitter via curl

Terminal - Update twitter via curl
curl -u user:pass -d status="Tweeting from the shell" http://twitter.com/statuses/update.xml
2009-02-05 18:33:23
User: adamm9
137
Update twitter via curl

Alternatives

There are 7 alternatives - vote for the best!

Terminal - Alternatives
curl -u user -d status="Tweeting from the shell" http://twitter.com/statuses/update.xml
2009-08-05 02:24:01
User: matthewbauer
11

Doesn't require password (asks for it instead)

curl -u YourUsername:YourPassword -d status="Your status message go here" http://twitter.com/statuses/update.xml
2009-06-27 21:47:48
User: m33600
Tags: twitter
8

Found it on snipt, pok3, is it yours?

I put my user = m33600, the password and the status was my robot message:

Settima robot message: ALARM ZONE 3 (sent via command line).

Now bots may have their identity on twitter...

tweet () { curl -u UserName -d status="$*" http://twitter.com/statuses/update.xml; }
2009-11-07 06:54:02
User: bartonski
Tags: twitter tweet
8

This version of tweet() doesn't require you to put quotes around the body of your tweet... it also prompts you for password. It will still barf on a '!' character.

curl -u twitter-username -d status="Hello World, Twitter!" -d source="cURL" http://twitter.com/statuses/update.xml
2009-12-08 14:54:33
User: MyTechieself
Tags: twitter curl api
6

An improvement of the original (at: http://www.commandlinefu.com/commands/view/2872/update-twitter-via-curl) in the sense that you see a "from cURL" under your status message instead of just a "from API" ;-) Twitter automatically links it to the cURL home page.

tweet(){ curl -u "$1" -d status="$2" "http://twitter.com/statuses/update.xml"; }
2009-08-23 16:56:24
User: Code_Bleu
2

Type the command in the terminal and press enter to create the tweet() function. Then run as follows:

tweet MyTwitterAccount "My message goes here"

It will prompt you for password. Make sure that you use escape "\" character in message for showing varialbles or markup.

Know a better way?

If you can do better, submit your command here.

What others think

Be carefull not to do that in a multi-user machine, since your password will be visible in the process listing for as long as curl is running.

Comment by kov 80 weeks and 1 day ago

If you leave out `:pass` (your password), you will be able to enter your password later in a more secure manner.

Comment by sirlancelot 78 weeks and 1 day ago

Also note that you can't use an "!" as bash will error out with

bash: !": event not found
Comment by XtCrAvE 76 weeks and 1 day ago

or $history -c once you do that... [of course to clear the hisory]

Comment by chanux 75 weeks and 3 days ago

regarding bash history and security: you can also put a space in front of a command to keep it out of your .bash_history (pressing up won't show it)

curl etc...etc...

http://www.commandlinefu.com/commands/view/1512/execute-a-command-without-saving-it-in-the-history

Comment by sudopeople 74 weeks and 6 days ago

This is resulting in 403 (Forbidden) errors today:

403 Forbidden: The server understood the request, but is refusing to fulfill it.

Comment by alesplin 72 weeks and 6 days ago

Note: if cURL not installed, install it (ubuntu) :

sudo apt-get install curl

Comment by cmdnix 56 weeks and 3 days ago

You can use ! just use 'single quotes'

Comment by mandroid 16 weeks and 6 days ago

Just start the command with a space (if it includes your password)so that its not stored in your .bash_history file. its safer that way.

Comment by nssy 9 weeks and 3 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts