interworking issue with native Windows, depending on terminfo

Brian Inglis Brian.Inglis@SystematicSW.ab.ca
Tue Oct 27 17:39:23 GMT 2026


On 2026-10-27 04:32, Thomas Wolff wrote:
> Hi,
> please see https://github.com/microsoft/WSL/issues/42032#issuecomment-6432254350
> "cygwin is not providing the native process a proper console when the matching 
> terminfo is missing".
> 
> If terminfo is not present (e.g. /usr/share/terminfo/78/xterm, or xterm-new, or 
> xterm-256color, whichever is set via $TERM), and you run wsl.exe, the WSL shell 
> will be in non-interactive/non-pty mode, not show a prompt, not handle signals 
> (so, e.g. ^C would exit WSL), etc.
> One use case would be a standalone application with cygwin bundled but not 
> terminfo.
> While a standalone package developer will notice this and eventually also 
> provide terminfo files, I don't see a logic connection that would make pty/ 
> console or whatever is missing here depend on terminfo.

Both wslbridge and mintty depend on cygwin dll which might make the console 
interface TERM dependent; why terminfo was made a Base package?

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry


More information about the Cygwin-developers mailing list