Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!amdahl!pacbell!att!ihuxy!vg55611
From: vg55611@ihuxy.ATT.COM (Gopal)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Wanted : Clearing files.
Message-ID: <2853@ihuxy.ATT.COM>
Date: 16 Feb 89 14:56:25 GMT
References: <804@haydn.kulesat.uucp> <1128@marlin.NOSC.MIL>
Reply-To: vg55611@ihuxy.UUCP (55611-Gopal,V.P.)
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 38

In article <1128@marlin.NOSC.MIL> jbjones@marlin.nosc.mil.UUCP (John B. Jones) writes:

>>By the way does anybody know of a way to program the function-keys under
>>MS-DOS ?
>
>This can be done easily from the command line or in the autoexec.bat by
>using the phrase
>
>prompt $e[{key code};{"statement you want"}[13]p

What the above really does is to program your ANSI.SYS to redefine your
keys (every time a prompt is displayed ons screen), so you have to have
ANSI.SYS.  I can also give you a program that I wrote called ANSISET
which will take a bunch of key mappings (or color changes etc.) 
as command line options.

>Most computer nerd books have a list of key codes somewhere in the 
>reference sections; if you don't have such inspired writings, the codes
>for F1 to F10 are 0;59 through 0;68.

My MS-DOS manual has a section on ANSI.SYS which is helpful.

>HOWEVER...This sort of thing might not work if you are currently using
>some kind of key redefining TSR(in that case, better do this stuff in
>the autoexec.bat) and it WON'T work if you don't copy ansi.sys to your

And a second side effect of doing something like this is that in the
case of some "well-behaved" programs that do not take over the keyboard
interrupt but require the use of functions keys, you lose the function keys.

>Johnjones
>jbjones@marlin.nosc.mil.UUCP

Venu P. Gopal
UUCP:	att!ihuxy!vg55611
Internet: vg55611@ihuxy.att.com
BITNET: com%"vg55611@ihuxy.att.com"   or   com%"vg55611%ihuxy@research.att.com"
Save 500 million keystrokes a day; silence those silent letters forever.