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

delete multiple files with spaces in filenames (with confirmation)

Terminal - delete multiple files with spaces in filenames (with confirmation)
ls -Q * | xargs -p rm
2010-01-27 02:46:49
User: temp_reg
Functions: ls xargs
1
Up
Down
delete multiple files with spaces in filenames (with confirmation)

ls -Q will show the filenames in quotes. xargs -p rm will print all the filenames piped from ls -Q and ask for confirmation before deleting the files.

without the -Q switch, if we have spaces in names, then the files won't be deleted.

Show sample output | Add to favourites | Report as malicious

Alternatives

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

I'd add the -i switch to rm to be sure there will be confirmation.

Or an backslash \ before rm to override any alias set.

Comment by CodSpirit 173 weeks and 2 days ago

rm -i doesn't work with xargs.

Comment by temp_reg 173 weeks and 2 days ago
rm -i *

or, if you just want to delte files with spaces (why?)

rm -i *\ *
Comment by Escher 173 weeks and 2 days ago

@CodSpirit the xargs -p option is playing the role of rm's -i option here. -p means "interactive" so it will print out the command it's about to run, and ask you if it should be run. To get the one-by-one behavior you could add -n 1 so that it asks you for each file one at a time so you know exactly what command is being run

ls -Q * | xargs -p -n 1 rm

xargs invokes the commands directly (forking the processes without the shell, afaict) so I don't think there is any chance for a shell alias for rm being used.

Comment by bwoodacre 173 weeks and 1 day ago

@ Escher, with rm -i, we'll have to confirm the deletion for each file. but with this method, all the files about to be deleted will be displayed at once, and a single confirmation will delete the files.

Comment by temp_reg 173 weeks and 1 day ago

xargs is inherently bad at dealing with special characters. To see the problem try this:

touch '12" record'

ls -Q * | xargs -p rm

Comment by unixmonkey8046 173 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts