Mail Archives: djgpp-workers/2002/05/14/14:20:29
> Date: Tue, 14 May 2002 19:13:57 +0100
> From: Laurynas Biveinis <lauras AT softhome DOT net>
>
> [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.
- Raw text -