Create a bunch of dummy files for testing

touch {1..10}.txt
Sometimes I need to create a directory of files to operate on to test out some commandlinefu I am cooking up. The main thing is the range ({1..N}) expansion.

11
By: slaney
2009-03-09 12:54:45

These Might Interest You

What Others Think

I do that one. If I need a file that has some content, but it doesn't matter what, I do this one: for i in {1..10}; do cat $RANDOM > $i.txt; done Although, I prefer to have these files isolated for easy cleanup, so I usually start with cd `mktemp -d`
goodevilgenius · 484 weeks and 6 days ago
Hi, my proposal is to substitute ... cat ... with ... echo ...
zwergnase · 484 weeks and 6 days ago
Only if you want it to work...
kjdames · 484 weeks and 6 days 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?

commandlinefu.com 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.

» 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: