Path: utzoo!attcan!uunet!cs.utexas.edu!usc!apple!brutus.cs.uiuc.edu!tut.cis.ohio-state.edu!bloom-beacon!kailand.kai.COM!pwolfe
From: pwolfe@kailand.kai.COM (Patrick Wolfe)
Newsgroups: comp.mail.mush
Subject: macros that end in tilde
Message-ID: <8907280259.AA23361@kailand.kai.com>
Date: 28 Jul 89 02:59:37 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: Kuck and Associates, Inc., 1906 Fox Drive, Champaign IL 61820, voice 217-356-2288, fax 217-356-5199
Lines: 34

There appears to be a bug in Mush 6.5.6 handling macros activated by codes that
end in tilde's.  I'm trying to use the "map" command in line mode to define
commands to be executed when I press my VT220 compatible terminal's function
keys.  These function keys all end with a tilde.

The command in my .mushrc is:
        map '\E[20~' "echo f9 was pressed\n"

When I press function key "f9" after a prompt, instead of displaying the
message, mush usually pauses for a second, then displays '^E[20~', exactly what
the function key sent, on the command line, as though it didn't recognize the
macro.  I say usually, because once in a while it works correctly, but about
90% of the time it doesn't.  I can't isolate any conditions that cause it to
fail repeatedly.

If I manually type the key sequence in, it executes the macro correctly, and
displays my message.  If I press the function key and then any other key
immediately (such as the space bar), the macro is expanded perfectly.  If I map
the code leaving off the tilde, it works every time, except for the unfortunate
side effect of having a tilde placed at the beginning of the next command
line.

Can someone please help me find a way to get mush to reliably handle my
function key macros?


        Patrick Wolfe   (pat@kai.com, kailand!pat)
        System Manager, Kuck & Associates, Inc.


-- 

        Patrick Wolfe   (pat@kai.com, kailand!pat)
        System Manager, Kuck & Associates, Inc.