This is a followup to #118 .
The workaround there was to add a flag that the user can provide, in order to not use atomic screen updates.
Ideally the user should not be bothered with this, and it should just be detected.
And apparently some terminals (cmd.exe, it seems), does not silently drop these escapes it doesn't support.
Describe the solution you'd like
Some sort of autodetection. And failing that, some heuristics.
Describe alternatives you've considered
The only options are support detection, or a whitelist or blacklist of terminals.
Or maybe just blacklist Windows?
Additional context
See #118
This is a followup to #118 .
The workaround there was to add a flag that the user can provide, in order to not use atomic screen updates.
Ideally the user should not be bothered with this, and it should just be detected.
And apparently some terminals (
cmd.exe, it seems), does not silently drop these escapes it doesn't support.Describe the solution you'd like
Some sort of autodetection. And failing that, some heuristics.
Describe alternatives you've considered
The only options are support detection, or a whitelist or blacklist of terminals.
Or maybe just blacklist Windows?
Additional context
See #118