Today I learned about the command zcat and how it is being used in a production situation where I think gunzip would make way more sense because i found someone years ago wrote a job redirecting the output of zcat into a text file... which is exactly what gunzip would have done if you just fucking unizpped it....
- they/them
- youtube.com/c/MicolitheSA
| Micolithe |
|---|
| Agender |
| 36 years old |
| Philadelphia, PA |
 |
| Last Login: 08/30/2007 |
Agender Enby, Trans, Gay, AND the bearer of the gamer's curse. Not a man, not a woman, but instead I am puppy.
I got a fat ass and big ears.
--
Yes I did the cooking mama Let's Play way back when. I post alot about Tech (mostly how it sucks) and Cooking and Music and Television Shows and the occasional Let's Play video
💖@FadeToZac
--
We all do what we can ♫
So we can do just one more thing ♫
We can all be free ♫
Maybe not in words ♫
Maybe not with a look ♫
But with your mind ♫
Youtube
youtube.com/user/MicolitheSATwitch
twitch.tv/micolitheYou must log in to comment.
in reply to @micolithe's post:
i find there is one useful behavior to gzip -dc file.txt.gz > file.txt (which I assume zcat mirrors?), which is that if the file is corrupt, gzip -dc file.txt.gz > file.txt will still send as much uncorrupted text as exists to the text file, whereas gzip -d file.txt.gz (and i assume gunzip?) will delete the in-process file, and error out leaving no text decompressed.
i do not know if that's a useful behavioral distinction, or anything the authors were thinking about, but like there is at least a reason to do this in some situations.