Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!samsung!sol.ctr.columbia.edu!emory!gatech!purdue!haven!wam!cscwam.umd.edu!dmb From: dmb@cscwam.umd.edu (David M. Baggett) Newsgroups: comp.sys.atari.st.tech Subject: Weird Keyboard Behavior with Gulam when Typing Quickly [also Elvis] Message-ID: <1991Feb8.184443.26162@wam.umd.edu> Date: 8 Feb 91 18:44:43 GMT Sender: usenet@wam.umd.edu (USENET Posting) Organization: University of Maryland at College Park Lines: 25 I've been using Gulam for quite some time and started using Elvis a few months ago. The problem is that when I type certain pairs of capital letters very quickly Gulam seems to convert them to function key scan codes. E.g., I type "MI" quickly and Elvis gives me "M#f3I". This happens quite frequently, probably because I never actually learned to touch-type, but rather acquired a sort of "burst-mode" method, the eventual evolution of several-finger hunt-and-peck. (What you get for learning to program at age 9, I guess.) Anyway, I traced the problem to Gulam. Try typing "MI" on the command line, and Gulam will say "Mark set" or something like that, as though you typed F3. (I suppose it could be something in the AUTO folder as well, but since I know Gulam replaces the keyboard handler I am assuming it's its fault.) Does anyone know how I can fix this? Is there some way to turn off Elvis' expansion of Shift-F3 into #f3? It's driving me crazy! And I really don't want to go back to LeVee (32K file limit), or STevie, since I otherwise like Elvis a lot. At the least, can I get source to Elvis and compile out the function key support? Thanks all, Dave Baggett dmb%wam.umd.edu@uunet.uu.net