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/
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.
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.
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:
the sed way to print a linhe with 50 hyphens
Convert all PNG images in directory to JPEG using ImageMagick, and delete the old PNG images.
Route output to notify-send to show nice messages on the desktop, e.g. title and interpreter of the current radio stream
When you run an X program from a terminal you can see any errors. But when it's run from another X program (eg from a menu item, from your fluxbox 'keys' file etc) it might just die and you see nothing (except perhaps in .xsession-errors). Instead, launch it via this command and you'll see the termination status, stderr and stdout.
eg: "xlaunch firefox" or "xlaunch 'echo stdout; echo stderr >&2; false'":
'echo stdout; echo stderr >&2; false' failed with error 1
If you gzip an empty file it becomes 20 bytes. Some backup checks i do check to see if the file is greater than zero size (-s flag) but this is no good here. Im sure someone has a better check than me for this? No check to see if file exists before checking it's size.
terms inclosing '()' must be enclosed by "" (soft quotes)
bash variables must be referenced: b $x/$y
ugly bracket checking (balanced, fractions...)
default precision 2
Exclude 400 client hosts with NFS auto-mounted home directories.
Easily modified for inclusion in your scripts.
A bit different from some of the other submissions. Has bold and uses all c printable characters. Change the bs=value to speed up and increase the sizes of the bold and non-bold strings.
Manpages, command summaries, and pretty much everything else usually have the information you're most likely to want at the beginning. Seeing just the last 40 or so lines of options from a command that has 100 is not super useful, and having to scroll up each time you want to glance at something is spastic.
Run this and then do something like
p do vi --help
and you'll get the first screen(-mostly-)full of vi's usage info and options list
to page down, and
to page up.
To see the current page again:
Also useful for situations like
p do aptitude search ~dsmorgasbord
#p sudo aptitude -r install libwickedawesome-perl-snoochieboochies
p sudo aptitude -r install libwickedawesome-perl-snoochieboochies snazztasticorama-dev-v0.∞
where you're using readline up-arrow, HOME, END, etc., to quickly recall commented commands.
For the unaware, that option to aptitude search will bring up all of the packages whose descriptions contain the string "smorgasbord". Depending on your distro, there could potentially be hundreds of them.
man 5 shadow
I think it's more reliable, because
dont show "locked" but "L" as second field on my Archlinux for a particular user.
( unixhome alternative ).
This can show all ls colors, with a demo.
Displays a scrolling banner which loops until you hit Ctrl-C to terminate it.
Make sure you finish your banner message with a space so it will loop nicely.
on this way we can define the body too
in loop, until the last port (65535), list all opened ports on host.
in the sample I used localhost, but you can replace with any host to test.
Hi glaudiston, you can save a few chars by leaving out cat and pipe and still enjoy the added flexibility.
Yep, is hard, but is a way more flexible using pipe.
For vi(m) users :
Add it in your ~/.bashrc
Add an "exit" @ the end if you are masochist ;)
@putnamhill, no need if statement in that case.
&& is a AND and || is a OR
Also works in places where reset does not.
Like the tiltle said, you can use an argument too ( the interface )
will show only the IP of this interface and the public IP
( tested with Linux )
You can add that function in ~/.bashrc, then
Now you are ready to call this function in all your terms...