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).

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
-2
Up
Down
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").

Show sample output | Add to favourites | Report as malicious

Alternatives

There are 6 alternatives - 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 212 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 189 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 183 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts