prevent accidents and test your command with echo

echo rm *.txt
if you're using wildcards * or ? in your command, and if you're deleting, moving multiple files, it's always safe to see how those wildcards will expand. if you put "echo" in front of your command, the expanded form of your command will be printed. It's better safe than sorry.
Sample Output
rm 1.txt 2.txt 3.txt 4.txt

2010-10-27 07:26:26

1 Alternatives + Submit Alt

What Others Think

nice idea.. a good default way to test parameter expansion if your inputrc doesn't auto-expand already.
AskApache · 602 weeks and 6 days ago
In terms of preventing some rm-related accidents, you may also want to install safe-rm: On Debian/Ubuntu: apt-get install safe-rm
fmarier · 602 weeks and 2 days ago
If you hit Meta-* (usually Alt+Shift+8), then inputrc will expand all the wildcards inline. e.g. rm d*<meta-*> Becomes: rm dave dog dull Then you can hit enter, or ctrl-c
flatcap · 602 weeks and 1 day ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. 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.

Share Your Commands

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.


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: