Live data from Hacker News

Inspect ANSI control codes and escape sequences

ansi.tools

41–50 of 52 posts

Re: Inspect ANSI control codes and escape sequences

#42
post #27
post #24

Earlier quoted context omitted.

The parser has, but not the HTML renderer indeed. Using a third-party lib for that currently, but noticed the limitations too. Might replace it with my own!

Great! Next step: torturetest.vt

Does it crash the tester?

https://invisible-island.net/ncurses/tctest.htm

Re: Inspect ANSI control codes and escape sequences

#43
post #30
post #5

Neat tool, I could see this being handy for debugging TUI tools. I noticed that it works with _escaped_ ESC characters ("\x1b", "\u001b", "\033") but it didn't recognize raw ESC characters that I had in my clipboard. It might be useful to support those (maybe highlight them similarly to how VS Code highlights whitespace characters). The characters show up as numbered unicode error glyphs (I'm on Firefox, if that help…

Thanks, this is great feedback. I'll see what I can do, stay tuned.

Raw input should be cool now (there's "raw" in the examples as well)

Re: Inspect ANSI control codes and escape sequences

#44
post #27

Earlier quoted context omitted.

Great! Next step: torturetest.vt

Does it crash the tester? https://invisible-island.net/ncurses/tctest.htm

There is some recovery in the lexer, but would love to learn what would make it crash! The url you provide gives a 404.

Re: Inspect ANSI control codes and escape sequences

#45
post #4

The revealing shibboleth is when people call it "ANSI". (-: "ANSI" is what people call it when they are working from paltry and incomplete samizdat doco of how this stuff works, from Microsoft's old ANSI.SYS appendix to its MS-DOS user manual, to innumerable modern WWW sites all repeating received wisdom. The thing to remember is that the "E" in "ECMA" does not stand for "ANSI". * https://ecma-international.org/publi…

> "ANSI" is what people call it when they are working from paltry and incomplete samizdat doco of how this stuff works

People just use "ANSI" as a shorthand for ANSI X3.64-1979. And that was the standard that DEC used for their VT100+ range of terminals, which in turn became the de facto standard from which most modern terminal emulators are derived. If you read the DEC documentation, you'll find many references to "ANSI standard", "ANSI controls", "ANSI colors", etc. I don't think this is because they were ignorant of the subject matter, considering that they were members of the committee that produced that standard.

And ECMA-48 is essentially just the European equivalent of ANSI X3.64, and was developed in parallel. But obviously an American company like DEC or Microsoft would more likely be working from the American version of the standard rather than the European one.

Re: Inspect ANSI control codes and escape sequences

#46
post #19

No support for blinking text.

Blinking text? You do not know me, but believe me, I have a special skills that I have developed for many years to deal with people like you. And if I find you I will CREOL you.

Bring it on. I’ll feed you your own form, you insignificant NUL character.

Re: Inspect ANSI control codes and escape sequences

#47
post #44

Earlier quoted context omitted.

Does it crash the tester? https://invisible-island.net/ncurses/tctest.htm

There is some recovery in the lexer, but would love to learn what would make it crash! The url you provide gives a 404.

  s/htm/html/
I.e. https://invisible-island.net/ncurses/tctest.html>
Post reply on HN