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.

UpGuard checks and validates configurations for every major OS, network device, and cloud provider.

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:



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!

Top Tags



Quickly determine lines in terminal

Terminal - Quickly determine lines in terminal
_llines=100; while [ $_llines -gt 1 ]; do echo $_llines; _llines=$(($_llines-1)); done
2009-04-29 00:19:45
User: romulusnr
Functions: echo
Quickly determine lines in terminal

You've opened a terminal window and you've connected off to a remote host that didn't pick up your terminal size, and all your curses and paging apps are screwed up as a result. You need to quickly determine how many lines are in your current terminal view (to feed into "stty rows X").


There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

Argh! Horrible.

How about using tput to determine screen characteristics:

(it's part of the ncurses library)

Number of lines:

tput lines

Number of columns

tput cols
Comment by flatcap 469 weeks and 1 day ago

Because that doesn't always work.

Right now I am going from Cygwin to a Linux box over ssh. I've resized the DOS window. But the change hasn't passed over. `tput lines` says: 71. But running my snippet shows that the terminal is actually 98 lines tall. tput is wrong because it gets its values from what the session THINKS is the terminal size. That doesn't necessarily match the real terminal size.

Comment by romulusnr 446 weeks ago

It wouldn't make any sense to do something like

stty rows `tput lines`

because stty and tput both work with the same values. The point is when the shell's idea of your terminal window size and your actual terminal window size is out of sync.

Comment by romulusnr 440 weeks and 1 day ago

Your point of view

You must be signed in to comment.