@[email protected] to [email protected] • 20 hours agozcat shouldn't error out if you try to zcat an uncompressed file, it should just output the damned file !message-square16fedilinkarrow-up156arrow-down18file-text
arrow-up148arrow-down1message-squarezcat shouldn't error out if you try to zcat an uncompressed file, it should just output the damned file !@[email protected] to [email protected] • 20 hours agomessage-square16fedilinkfile-text
minus-square@[email protected]linkfedilink12•19 hours agoYeah, it’s a pain. Leads to bad one liners: for i in $(ls); do zcat $i || cat $i; done
minus-square@[email protected]linkfedilink8•edit-25 hours agoBtw, don’t parse ls. Use find |while read -r instead. find -maxdepth 1 -name "term" -print |while read -r file do zcat "$file" 2>/dev/null || cat "$file" done
minus-square@[email protected]linkfedilink4•8 hours agoWon’t this cause cat to iterate through all files in the cwd once zcat encounters an issue, instead of just the specific file?
minus-square@[email protected]linkfedilinkEnglish1•edit-23 hours agoYou are correct. This probably produces something more similar to what you’d want the original command to do, but with better safely: find -- . -type f -regex '^\./[^/]*$' -exec sh -c -- 'for file in "${@}"; do zcat "${file}" || cat "${file}" || exit; done' sh '{}' '+' That assumes you want to interact with files with names like .hidden.txt.gz though. If you don’t, and only intend to have a directory with regular files (as opposed to directories or symbolic links or other types of file), using this is much simpler and even safer, and avoids using files in a surprising order: for i in *; do zcat -- "$i" || cat -- "$i" || exit; done Of course, the real solution is to avoid using the Shell Command Language at all, and to carefully adapt any program to your particular problem as needed: https://sipb.mit.edu/doc/safe-shell/
minus-square@[email protected]linkfedilink1•5 hours agoYeah, i was tired and had $file there first, then saw that you wanted to cat all in directory. Still tired, but i think this works now.
minus-square@[email protected]OPlinkfedilink2•edit-219 hours agoThanks ! But still we shouldn’t have to resort to this ! Also, can’t get the output through pipe for i in $(ls); do zcat $i || cat $i; done | grep mysearchterm this appears to work find . -type f -print0 | xargs -0 -I{} sh -c 'zcat "{}" 2>/dev/null || cat "{}"' | grep "mysearchterm" Still, that was a speed bump that I guess everyone dealing with mass compressed log files has to figure out on the fly because zcat can’t read uncompressed files ! argg !!! for i in $(ls); do zcat $i 2>/dev/null || cat $i; done | grep mysearchterm
Yeah, it’s a pain. Leads to bad one liners:
for i in $(ls); do zcat $i || cat $i; doneBtw, don’t parse ls. Use
find |while read -rinstead.find -maxdepth 1 -name "term" -print |while read -r file do zcat "$file" 2>/dev/null || cat "$file" doneWon’t this cause cat to iterate through all files in the cwd once zcat encounters an issue, instead of just the specific file?
You are correct. This probably produces something more similar to what you’d want the original command to do, but with better safely:
find -- . -type f -regex '^\./[^/]*$' -exec sh -c -- 'for file in "${@}"; do zcat "${file}" || cat "${file}" || exit; done' sh '{}' '+'That assumes you want to interact with files with names like
.hidden.txt.gzthough. If you don’t, and only intend to have a directory with regular files (as opposed to directories or symbolic links or other types of file), using this is much simpler and even safer, and avoids using files in a surprising order:for i in *; do zcat -- "$i" || cat -- "$i" || exit; doneOf course, the real solution is to avoid using the Shell Command Language at all, and to carefully adapt any program to your particular problem as needed: https://sipb.mit.edu/doc/safe-shell/
Yeah, i was tired and had $file there first, then saw that you wanted to cat all in directory. Still tired, but i think this works now.
Thanks !
But still we shouldn’t have to resort to this !
Also, can’t get the output through pipefor i in $(ls); do zcat $i || cat $i; done | grep mysearchtermthis appears to workfind . -type f -print0 | xargs -0 -I{} sh -c 'zcat "{}" 2>/dev/null || cat "{}"' | grep "mysearchterm"Still, that was a speed bump that I guess everyone dealing with mass compressed log files has to figure out on the fly because zcat can’t read uncompressed files ! argg !!!for i in $(ls); do zcat $i 2>/dev/null || cat $i; done | grep mysearchterm