Post B7tuEeKtdNW58TjZuy by rl_dane@polymaths.social
 (DIR) More posts by rl_dane@polymaths.social
 (DIR) Post #B7tuEe5IZN2WM6R7bc by JdeBP@tty0.social
       0 likes, 0 repeats
       
       As you can see, @rl_dane has me wondering whether anyone has ever written a sqz(1) #Unix #TextProcessing tool, to go alongside vis(1).https://tty0.social/@JdeBP/116834743954481512I am tempted to just quickly knock one together and put it into the #nosh toolset.RT: https://tty0.social/users/JdeBP/statuses/116834743954481512
       
 (DIR) Post #B7tuEeKtdNW58TjZuy by rl_dane@polymaths.social
       0 likes, 0 repeats
       
       @JdeBPYou mean like... awk/sed? ;)
       
 (DIR) Post #B7tuEeY0qc0Zn9s3MW by JdeBP@tty0.social
       0 likes, 0 repeats
       
       @rl_dane Well since vis(1) came about because of cat -v, it seems that there should be a sqz(1) because of cat -s .#Unix #TextProcessing #nosh
       
 (DIR) Post #B7tuEek47neKOXVg9I by rl_dane@polymaths.social
       0 likes, 0 repeats
       
       @JdeBPI feel like the 'cat -v considered harmful' folks would say to just use a shell/awk script, rather than writing a bespoke utility for that. ;)
       
 (DIR) Post #B7tuEewpMLrF27Ts2a by JdeBP@tty0.social
       1 likes, 0 repeats
       
       @rl_dane The 'cat -v considered harmful folks' (Kernighan and Pike) invented vis(1).> The preferred approach in this case is a separate program that deals with non-printable characters. We called ours vis […] because its job is to make things visible.I suspect that they would approve of sqz(1) likewise abstracted from cat -s, because they also said> cat isn’t […] for compressing multiple blank lines […] it’s for concatenating files.#vis #sqz #cat #Unix #TextProcessing #nosh