This is the mail archive of the
cygwin-developers@sources.redhat.com
mailing list for the Cygwin project.
fhandler_console
- To: cygwin-developers at cygwin dot com
- Subject: fhandler_console
- From: Egor Duda <deo at logos-m dot ru>
- Date: Tue, 20 Feb 2001 13:00:12 +0300
- Organization: DEO
- References: <16286062992.20010216183758@logos-m.ru><20010219214951.A23483@redhat.com>
- Reply-To: Egor Duda <cygwin-developers at cygwin dot com>
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.
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?
Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19