Hacker News .hnnew | past | comments | ask | show | jobs | submit | webpro's commentslogin

Some of the issues mentioned in this thread have been improved, including private CSI sequences, default param values, and cancellation + substitution.


What would prevent you from starting? Could be fun :)


Probably their free time budget


Time: There's other nerd projects I'd like to do.


Emojis and other unicode characters may or may not be rendered as a single-width character. I've been splitting hairs and strings.

The tool currently counts any unicode character as a single-width one.


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)


Thanks. Agreed. The way I see it, ignore the noise and there might be something in there.


That's some interesting feedback, thanks for sharing. I'll see what I can extract and apply from it. Please bear with me, this is only my initial take on the whole concept (and as you point out, it isn't that trivial). Didn't have much examples to be inspired by, but we're on our way anyway.


Thanks! It's all open source (including the tokenizer/parser), so feel free come collaborate on GitHub.


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




The lexer and parser handled it perfectly first try. The HTML renderer had a few issues though, but it's being rendered reasonably well now. The torture test has been added to the package tests and to the website as an example.



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



Thanks for sharing, haven't seen that one yet. Will see if I can borrow ideas from it.


At least I tried to make it look like a 1993 website


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: