X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f Date: Tue, 14 May 2002 21:18:43 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: lauras AT softhome DOT net Message-Id: <6480-Tue14May2002211843+0300-eliz@is.elta.co.il> X-Mailer: emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9 CC: djgpp-workers AT delorie DOT com In-reply-to: <1997943472.20020514191357@softhome.net> (message from Laurynas Biveinis on Tue, 14 May 2002 19:13:57 +0100) Subject: Re: emacs under w2k References: <1997943472 DOT 20020514191357 AT softhome DOT net> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Tue, 14 May 2002 19:13:57 +0100 > From: Laurynas Biveinis > > [Sorry for delayed reply, there are some things keeping me busy.] I know what you mean ;-) > Now I've emacs 21.2, which is behaving in exactly the same way. Okay, that much I expected. > And of > course I can use any help with sources - where are the sources dealing > with keyboard input? See the function dos_rawgetc defined on msdos.c. In general, most of the DOS-specific code is in msdos.c, and the rest is in dosfns.c. > Also, as you've described above another problem > with programs catching SIGINT etc. - does emacs install its own signal > handlers for these? No, it doesn't. Moreover, it switches stdin to raw/binary mode, and thus disables SIGINT from Ctrl-C entirely. (You can still produce SIGINT with Ctrl-BREAK, though.) That's what puzzles me: the Emacs code plays it so safe that I don't know where to start looking for possible problems. It uses only standard video modes, goes through BIOS for keyboard input, and reads the mouse via Int 33h. Direct screen access through dosmemput, dosmemget, and ScreenRetrieve is about the most ``fancy'' code you will see there.