Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!hsdndev!husc6!genrad!genrad.com!jpn From: jpn@genrad.com (John P. Nelson) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: ms_sh-1.6.4 question (^P for Previous) Message-ID: <40486@genrad.UUCP> Date: 25 Jan 91 17:23:13 GMT References: <2034@odin.cs.hw.ac.uk> Sender: news@genrad.UUCP Reply-To: jpn@maxwell.genrad.COM (John P. Nelson) Organization: GenRad, Inc., Concord, Mass. Lines: 28 >>It seems to me that ms_sh tries to start echoing stuff to the printer >>on a ^P, even if I use it for something else in the sh.ini file. Is >>there a way to use ^P for Previous? Please don't suggest binding... > >I've found this problem too. Some bit of DOS (probably deep down in the >BIOS) intercepts ^S, ^P & ^N which is a bit of a pain for us Emacs/tcsh >addicts who keep turning the printer echo on when we hit ^P or ^N. I've been holding off from replying to this because I assumed that there would be a flood of answers. No, it isn't the BIOS doing ^P and ^S processing (I don't think ^N does anything, does it?), it is the DOS CON: driver. There are two very simple ways for a programmer to avoid this effect: #1: instead of asking DOS for input characters, you can use the BIOS functions to read the keyboard (Actually, certain DOS functions will bypass the ^P ^S processing, too). #2, the special processing can be disabled by using the MSDOS "IOCTL" function: IOCTL can be used to put the console into RAW mode, so it won't do any special processing of input characters. If someone's emacs or communications program is using the COOKED DOS input functions to get keyboard data, then that program is BUGGY, and should be FIXED. john nelson uucp: {decvax,mit-eddie}!genrad!jpn domain: jpn@genrad.com