|
Size: 1148
Comment:
|
Size: 1429
Comment: fixes. fixes are good.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 24: | Line 24: |
| To do it recursively, you should use a loop, plus the [[UsingFind|find]] command: | To do it recursively, use [[UsingFind|find]]: {{{ # Bourne find . -name '*.gz' -type f -exec do-something {} \; }}} If you need to process the files inside your shell for some reason, then read the `find` results in a loop: |
| Line 28: | Line 35: |
| while read file; do echo "$file" # do something with "$file" |
while IFS= read -r file; do echo "Now processing $file" # do something fancy with "$file" |
| Line 34: | Line 41: |
| For more hints in this direction, see [[BashFAQ/020|FAQ #20]]. To see why the `find` command comes after the loop instead of before it, see [[BashFAQ/024|FAQ #24]]. | This example uses ProcessSubstitution (see also [[BashFAQ/024|FAQ #24]]), although a pipe may also be suitable in many cases. However, it does not correctly handle filenames that contain newlines. To handle arbitrary filenames, see [[BashFAQ/020|FAQ #20]]. |
How can I run a command on all files with the extension .gz?
Often a command already accepts several files as arguments, e.g.
zcat -- *.gz
On some systems, you would use gzcat instead of zcat. If neither is available, or if you don't care to play guessing games, just use gzip -dc instead.
The -- prevents a filename beginning with a hyphen from causing unexpected results.
If an explicit loop is desired, or if your command does not accept multiple filename arguments in one invocation, the for loop can be used:
# Bourne
for file in ./*.gz
do
echo "$file"
# do something with "$file"
doneTo do it recursively, use find:
# Bourne
find . -name '*.gz' -type f -exec do-something {} \;If you need to process the files inside your shell for some reason, then read the find results in a loop:
# Bash
while IFS= read -r file; do
echo "Now processing $file"
# do something fancy with "$file"
done < <(find . -name '*.gz' -print)This example uses ProcessSubstitution (see also FAQ #24), although a pipe may also be suitable in many cases. However, it does not correctly handle filenames that contain newlines. To handle arbitrary filenames, see FAQ #20.