Closed MoSal closed 5 years ago
Can I at least get a yes/no/maybe on this one?
Sorry, this fell off my radar. Instead of importing the xterm definitions like this, couldn't you set the name to "xterm-256color" and then fallback on the is_ansi
check in the from_name
function (I'd like to avoid bundling the db if possible).
(please do bug me when I don't respond)
Done. Although this is not ideal, as the fallback definition is too basic.
@MoSal thanks!
Windows people seem to be fine with this: Microsoft/WSL#1446
I still think a precise terminfo file with the list of supported sequences documented in the below link would be ideal: https://docs.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences
But I didn't find such a file. And I don't know how to generate one easily.
~~A copy of xterm-256color terminfo file is included at compile-time. I copied it from ncurses 6.1.~~
~~With this commit, term should be on par with ansi_term for Windows 10 users.~~
Edited to fallback to a basic ANSI terminal.