Brent,
> I know most Poplog users are running under some Linux
> or
> UNIX variant (I certainly am at home), but my work
> system is Windows. Unfortunately, the various
> documents
> on VED refer to certain keys (such as MARKHI/MARKLO)
> with no information on what these keys are mapped to
> on a standard PC keyboard.
There are three answers to this:
(a) There are Escape and Ctrl Key sequences which I think
are the same (by default) in all versions of Ved and Xved
and are documented in HELP vedkeys. For example, that includes:
ESC m Mark start of range MARKLO
ESC M Mark end of range MARKHI
(b) Frequently used keyboard functions are mapped onto function
keys for easier use, but over the years different sets of mappings
were developed. The bham package for linux/unix users tries to
make this more uniform, with F1 mapped to MARKLO, and F2 mapped
to MARKHI, but I think it is different under windows.
You can find the current Ved functions invoked by any function
key or key sequence as follows:
Press:
ENTER hkey RETURN
You should then get this displayed
(Please press the key. If no response, press more keys)
Press the key F1 and you'll find what's mapped onto F1, if anything is
and be directed to a Ref file entry for it (if there is one).
You may find that the two keys you want are F7 and F8 in windows poplog,
until it gets changed to be consistent with the linux/unix version.
(c) If the default mappings don't suit you, you can map any function key
or key sequence to any Ved function, including new ones that you define,
using vedsetkey, or the vedset syntax.
(See HELP vedsetkey, HELP vedset).
But first you have to find out what character sequences are transmitted
by each of the function keys you want to use.
A useful tool for doing this is the procedure vedinkeys, described in
REF vedprocs. You can invoke it from Ved's command line thus:
ENTER :vedinkeys(false) RETURN
If you use it a lot you may find it easier to put this in your
vedinit.p file:
define ved_inkeys();
vedinkeys(false);
enddefine;
Then you can invoke it as
ENTER inkeys RETURN
Once it starts running, press all the function keys you wish to
interrogate (separated by spaces) and terminate with CTRL C, or ESC
pressed three times.
If you remember which keys you pressed(!) you'll have a record in the
Ved buffer of the character sequences transmitted by each of them.
Using those you can insert calls of vedsetkey in your vedinit.p file
within the definition of a procedure vedinit that you define.
(See REF vedinit).
E.g. If F1 transmits four characters
ESC 9 9 ~ (randomly chosen example)
you can make it invoke vedmarklo thus:
vedsetkey('\^[99~', "vedmarklo");
The double quote marks are not essential but allow you to redefine the
procedure without having to redo the vedsetkey command, which is
sometimes useful for temporary effects.
Aaron
|