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

Replace spaces with tabs & format file source recursively within a directory

Terminal - Replace spaces with tabs & format file source recursively within a directory
find . -type f -name \*.php | while IFS="" read i; do expand -t4 "$i" > "$i-"; mv "$i-" "$i"; done
2011-04-08 12:53:14
User: flatcap
Functions: expand find mv read
-4
Up
Down
Replace spaces with tabs & format file source recursively within a directory

Recursively find php files and replace tab characters with spaces.

Options:

"\*.php" -- replace this with the files you wish to find

"expand" -- replace tabs with spaces (use "unexpand" to replace spaces with tabs)

"-t4" -- tabs represent 4 spaces

Note: The IFS="" in the middle is to prevent 'read' from eating leading/trailing whitespace in filenames.

Add to favourites | Report as malicious

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
find $DIR -name *.php -exec vim -u NONE -c 'set ft=php' -c 'set shiftwidth=4' -c 'set tabstop=4' -c 'set noexpandtab!' -c 'set noet' -c 'retab!' -c 'bufdo! "execute normal gg=G"' -c wq {} \;
2011-04-08 11:42:45
User: ruslan
Functions: find vim
Tags: vim source spaces tab format
-2
Up
Down
Replace spaces with tabs & format file source recursuvely within a directory

The sample command searches for PHP files replacing tabs with spaces.

-u NONE # don't use vimrc

Instead of

retab!

one may pass

retab! 4

for instance.

Look at this http://susepaste.org/69028693 also

Comments (0) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

flatcap, it expands/unexpands *all* file contents. Isn't it?

While my command uses smart vim formatting to *indent* using tabs, not touching those in strings, for instance

Comment by ruslan 110 weeks and 6 days ago

Really? Unfortunately, I can't get your command to work.

From the vim help on retab: Careful: This command modifies any characters inside of strings in a C program. Use "\t" to avoid this (that's a good habit anyway).

By adding --initial to expand (or --first-only to unexpand), it will only work on leading whitespace.

As a heavy user of vim, I'd have done this by macro or bufdo. Spawning vim for every file will really slow things down.

Comment by flatcap 110 weeks and 6 days ago

flatcap, what about constructions like

$a = array( 'key1' => '12', 'longlongkey' => 'someghing', 'second-long-k' => 12.34, );

?

Comment by ruslan 110 weeks and 6 days ago

It didn't format like what I mean. Look at this: http://susepaste.org/28853675

Comment by ruslan 110 weeks and 6 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts