Mail Archives: cygwin-developers/2001/02/20/12:22:55
On Tue, Feb 20, 2001 at 01:00:12PM +0300, Egor Duda wrote:
>Hi!
>
>i've looked a bit deeper into fhandler_console code, and think it
>needs more fixing. for example, this command:
>
>echo -e -n "\033[?" && echo -e "1000h"
>
>won't enable mouse events reporting ("saw_question_mark" should be
>persistent across write calls) and several other issues. so i think
>several variables which are related to console "state" should be made
>members of class fhandler_console.
I agree. I was just noticing the static variables yesterday.
>the only thing i want to get advice on -- is fhandler_console::dup
>ever called? i've never seen so. if i miss something and it is
>called, then all such "persistent state" information should be
>stored not in fhandler_console itself, but in separate structure
>referenced from fhandler_console and common for all fhandler_console
>instances.
>
>Chris, can you tell if your cygheap code eliminates the need for
>fhandler_console::dup?
No, fhandler_console::dup isn't really related to cygheap. It is just
a method that is called automatically from dup().
cgf
- Raw text -