Re: Seriously, who doesn't just load log files into a boring old programmer's editor
> An editor which only understood plain 7-bit ASCII
>> display as hex/octal/binary etc etc
UTF-8, UCS-16, ShiftJIS all fall under "etc" in my book :-)
> like piping through ansi2txt would.
The whole point of having a *halfway decent* text editor is that it has loads and loads of display filters so that you don't pipe data through anything, you just select the filter - and still keep *all* of the original buffer contents unmodified. Oh, and a good grep function preferably works over the displayed/filtered results, but switching to a text/language mode works as well.
A really, really good editor lets you mark sections of the buffer and select the display filter on each (e.g. use a syntax highlighter for this bit, but haven't seen that in yonks, sigh. Not without using, say, a Markdown display mode and hoping the markup is in place; but I digress, this is about untrusted files).
That way you can not only find the suspicious entry but you can place the cursor there, switch to, say, hex display (or, even better, "show ESC codes") and immediately spot the naughty sequence they hoped would take over your terminal.