Cygwin disables command-line editing in ConPTY

[Eric Pement]

I have used Cygwin grep and a few other Cygwin tools (sort, nl, etc.) in conjunction with TCC for a long time. However, I now discover that using Cygwin grep in a TCC session (v36.50.71) now produces an undesirable side-effect when TCC is running in a pseudoconsole (ConPTY) : it disables TCC's command-line editing (L/R cursor keys, some control-keys), my command history (Up/Dn cursor keys, PgUp, PgDn), and all function keys.

It doesn't do this when TCC is running in another console (e.g., ConEmu).

I don't know of any way to re-enable the command-line and history in TCC other than exiting and restarting a new TCC session.

 

[Charles Dye]

Can you reproduce this in Windows Terminal?

 

[vefatica]

I have many of Cygwin's tools and I use Cygwin's grep interchangeably with Gnu's. And I use one or the other tens of times a day. They are nearly the same thing (see below). I have never seen anything like what you describe. Can you give steps to reproduce bad behavior?

v:\> d:\gnu\grep -V
grep (GNU grep) 3.0
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Mike Haertel and others, see <http://git.sv.gnu.org/cgit/grep.git/tree/AUTHORS>.

v:\> d:\c64\grep -V
grep (GNU grep) 3.10
Packaged by Cygwin (3.10-1)
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Mike Haertel and others; see
<https://git.savannah.gnu.org/cgit/grep.git/tree/AUTHORS>.