Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!agate!agate.berkeley.edu!thewalt From: thewalt@canuck.ce.berkeley.edu (C. Thewalt) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: ms_sh-1.6.4 question (^P for Previous) Message-ID: Date: 23 Jan 91 16:55:05 GMT References: <2034@odin.cs.hw.ac.uk> Sender: usenet@agate.berkeley.edu (USENET Administrator) Organization: Dept. of Civil Engineering, University of California, Berkeley Lines: 20 In-Reply-To: scott@cs.hw.ac.uk's message of 22 Jan 91 11:24:29 GMT In article <2034@odin.cs.hw.ac.uk> scott@cs.hw.ac.uk (Scott Telford) writes: In article thewalt@canuck.ce.berkeley.edu (C. Thewalt) writes: >>... I am trying to rebind the keys (to act like emacs mode for >>a variety of unix shells) in sh.ini and all was going really well >>until I tried to bind Previous to ^P... > 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. Has > anybody found a fix for this? It can't be completely impossible since > the MKS Toolkit Korn Shell doesn't have this problem. Hmm. The ^S and ^N work for me (bound to ScanForeward and next respectively) but the ^P is making my life miserable. Chris -- Christopher Robin Thewalt These opinions are not necessarily thewalt@ce.berkeley.edu shared by my employer... University of California, Berkeley