Kyle Benesch

For converting into SDL Events you mean? Right now I can't think of anything other than spawning a thread for checking for terminal input from stdin. That'd be the only...

I'm not doing anything for this right now. I don't have the best setup to test with.

I tried my best to make compiling easier by explaining as much as possible in the [contributing guide](https://github.com/libtcod/libtcod/blob/develop/CONTRIBUTING.md). Right now anything other than VSCode is going to be awkward to...

Because it's to specifically target modern xterm consoles, rather than something far older like VT100. Not everything has support for the 24-bit color escape codes for example.

"console" implies that there's some kind of cross-platform console, which isn't the case. "ansi" doesn't mean anything on its own, terminal-wise.

It's hard to avoid the virtual terminal functions completely, and it's hard to say it's just ANSI escapes then these special functions are required to set it up correctly. My...

There's also https://invisible-island.net/xterm/ctlseqs/ctlseqs.html which is the most complete guide to these control sequences I know of, which just plainly calls them "XTerm Control Sequences" while also being the most clear...

Yeah, `TERM=xterm` is correct. And since the XTerm spec is what I was targeting I kind of ended up with the name xterm for the renderer. It doesn't really matter...

> What about calling it just "terminal" or "real-terminal" or something like that? I've said before that "console" and "terminal" are too generic. They imply some kind of universal cross-platform...

I guess I should mention that I don't plan on supporting a real terminal, at least initially. I'm not really into retro hardware. I'd call the renderer something like `VT100`...