4 ms·
It was the case indeed (many many years ago), we discussed at the anuualy curl hackers conference in Nuremberg back in 2017, but the only terminals that we mana
by igor_chubin 6y ago
It was the case indeed (many many years ago),
we discussed at the anuualy curl hackers conference in Nuremberg back in 2017, but the only terminals that we managed to find with the support of this were not younger than 2001.
Anyway, one can write a small filter, to cut any suspicious sequences from the output off, and add some wrapper like that to your bashrc:
curl() { [ -t 1 ] && curl "$@" | sanitize || curl "$@"; }
- rsapkf 6y agoI see you are using regular formatting for code/shell commands on your comments. Not that that's a problem but just a note you can use one of HN's comments formatting tips[0] for this. Text after a blank line that is indented by two or more spaces is reproduced verbatim. (This is intended for code.) [0]: https://news.ycombinator.com/formatdoc https://news.ycombinator.com/formatdoc
- igor_chubin 6y agoWow! That's cool. Let's try it curl() { [ -t 1 ] && curl "$@" | sanitize || curl "$@"; }
- igor_chubin 6y agoYes it works! The difference is minimal though (it was intentionally a one-liner)
- aloknnikhil 6y agoI actually stick to regular formatting on HN because of how terribly code formatting on HN renders on a phone. It doesn't wrap around when you format it as code and I have to scroll horizontally since the width is fixed. But it's probably OK for something like this code snippet.