Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!apple!altos!altos86!jerry
From: jerry@altos86.Altos.COM (Jerry Gardner)
Newsgroups: comp.editors
Subject: Re: vi's "too dangerous to map that" (was: Re: vi (vs VMS/EDT))
Message-ID: <36@altos86.Altos.COM>
Date: 28 Nov 89 17:14:29 GMT
References: <1989Nov14.223604.17418@cs.eur.nl> <1989Nov21.101249.15226@cs.eur.nl> <511@spinifex.eecs.unsw.oz>
Reply-To: jerry@altos86.UUCP (Jerry Gardner)
Organization: Altos Computer Systems, San Jose, CA
Lines: 34

In article <511@spinifex.eecs.unsw.oz> cameron@spinifex.eecs.unsw.oz (Cameron Simpson) writes:
 
>I tried to do this for a friend of mine a couple of years ago. That is, rig
>the keypad to act a bit like it does in EDT with `gold keys' (I think), and
>effectively be in insert mode all the time, etc. Much mapping of the tail
>ends of the escape sequences returned by the keys, etc. It partly worked,
>but eventually I ran up against vi's "too dangerous to map that" message.
>I can't find any doco about exactly what causes it, though it seems to be
>maps which cross insert/command mode boundaries. I'd love to know exactly
>what causes it. Then I'd have a better idea of how to work around it.
>	- Cameron Simpson


Here's the comment right before the code that prints the "too dangerous to
map that" message.


		/*
		 * We don't let the user rob himself of ":", and making
		 * multi char words is a bad idea so we don't allow it.
		 * Note that if user sets mapinput and maps all of return,
		 * linefeed, and escape, he can hurt himself. This is
		 * so weird I don't bother to check for it.
		 */


Interesting, eh?


-- 
Jerry Gardner, NJ6A					Altos Computer Systems
UUCP: {sun|pyramid|sco|amdahl|uunet}!altos86!jerry	2641 Orchard Parkway
Internet: jerry@altos.com				San Jose, CA  95134
I don't speak for Altos, they don't speak for me.       946-6700


Brought to you by Super Global Mega Corp .com