|
From: Eli Z. <el...@gn...> - 2015-01-06 17:46:27
|
> From: "Earnie" <ea...@us...>
> Date: Mon, 5 Jan 2015 18:04:21 -0500
>
> > From: Eli Zaretskii
> >
> > When a MinGW program linked with libncurses is run from the MSYS Bash, it
> > sees TERM=cygwin in the environment, and libncurses then uses the terminfo
> > data for that terminal, instead of using its internal Windows console driver.
> > However, using the cygwin terminfo entry doesn't work
> > well: e.g., the "clear to end of line" sequence ("\E[K" according to "infocmp
> > cygwin") appears verbatim instead of actually erasing text.
> >
> > I'm guessing that this doesn't work because the necessary magic for interpreting
> > these sequences is inside the MSYS DLL, and so won't work in any non-MSYS
> > program. Is that correct?
> >
>
> I believe so but does TERM=xterm help?
No, it doesn't.
Anyway, how is that different from unsetting TERM before running such
programs?
Or are you saying that it's safe to set TERM-xterm permanently in the
MSYS Bash session? I always thought that it is set to "cygwin" for a
reason. If not, then perhaps unsetting it is the solution?
|