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.

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

Commands by tmsh from sorted by
Terminal - Commands by tmsh - 5 results
for pid in `screen -ls | grep -v $STY | grep tached | awk '{print $1;}' | perl -nle '$_ =~ /^(\d+)/; print $1;'`; do screen -x $pid; done
2010-06-22 23:06:31
User: tmsh
Functions: awk grep perl screen
0

Personally, I save this in a one line script called ~/bin/sci:

#!/bin/bash

for pid in `screen -ls | grep -v $STY | grep tached | awk '{print $1;}' | perl -nle '$_ =~ /^(\d+)/; print $1;'`; do screen -x $pid; done

I also use:

alias scx='screen -x'

alias scl='screen -ls | grep -v $STY'

In vim: q: && v[cursor movement]y && [paste/edit/save to /tmp/tmp.vim] && move to window to modify && :so /tmp/tmp.vim
2010-05-12 03:03:40
User: tmsh
0

It's actually really helpful if you've done a lot of replaces in say a header file, and now you want to replace the same text in the source code file.

Create aliases for common vim minibuffer/cmd typos
2009-12-28 20:58:29
User: tmsh
Functions: vim
Tags: vim
1

Because entering ':' requires that you press shift, sometimes common command-line / mini-buffer commands will be capitalized by accident.

vim -
2009-11-10 22:25:36
User: tmsh
Functions: vim
-3

I don't know if you've used sqsh before. But it has a handy feature that allows you to switch into vim to complete editing of whatever complicated SQL statement you are trying to run.

But I got to thinking -- why doesn't bash have that? Well, it does. It's called '|'!

Jk.

Seriously, I'm pretty sure this flow of commands will revolutionize how I administer files. And b/c everything is a file on *nx based distros, well, it's handy.

First, if your ls is aliased to ls --color=auto, then create another alias in your .bashrc:

alias lsp='ls --color=none'

Now, let's say you want to rename all files that begin with the prefix 'ras' to files that begin with a 'raster' prefix.

You could do it with some bash substitution. But who remembers that? I remember vim macros because I can remember to press 'qa' and how to move around in vim. Plus, it's more incremental. You can check things along the way. That is the secret to development and probably the universe. So type something like:

lsp | grep ras

Are those all the files you need to move? If not, modify and re-grep. If so, pipe it to vim.

lsp | grep ras | vim -

Now run your vim macros to modify the first line. Assuming you use 'w' and 'b' to move around, etc., it should work for all lines. Hold down '@@', etc., until your list of files has been modified from

ras_a.h

ras_a.cpp

ras_b.h

ras_b.cpp

to:

mv ras_a.h raster_a.h

mv ras_a.cpp raster_a.cpp

mv ras_b.h raster_b.h

mv ras_b.h raster_b.cpp

then run :%!bash

then run :q!

then be like, whaaaaa? as you realize your workflow got a little more continuous. maybe. YMMV.

:set scroll=0
2009-10-10 07:38:27
User: tmsh
1

Resets the scroll parameter to the default (half the rows in the current window). The scroll parameter can be inadvertently set to 1, e..g., if you type '1 Ctrl-D' or '1 Ctrl-U' in normal mode.