Re: gold key for edt mode

[Thei Wijnen <t.wijnen@xxxxxxxxx>]

Hi,

On Windows there is "no problem" with the Numlock key, but when
I want to use JED on Linux there is a lot of trouble with
the Numlock key. In fact it may be best if we try to avoid
it completely in the future.

The additions I put in have to do with the fact that if you pick a 
different key for Gold, then Numlock starts to do strange things.
For instance it apears to be bound to "edt_line" as a result of
the fact that its generates \eOp in stead of \eOP. I do not
understand why this happens and thus I tried to get around that.

With the code at the beginning of edt.sl I solved these problems
and I could also take a different key like F12 and use that for Gold.
I can not use a Gold key that is being bound later in edt.sl
(second setkey is not allowed).

By the way, I forgot to mention in my previous mail that I use my
version of menus.sl, also to avoid second setkey actions when
the menus are turned on. And, the real changes to edt.sl are at the 
beginning of the file.
Then I put in the symbolic keynames when binding keys.
The third set of changes deals with having advanced scrolling near
the screen edges. This used to work only on the cursor keys and
now I have it also on all other keys that do cursor movements.
My bonus ;)

Concerning xkeys for / * - :  In xjed they appear always as
/ * - and are inserted as text in your file. The reason is simple:
in xkeys.c one can see that these keys do not generate en escape
sequence, but the simply send their single character / * or -.
These can not be distincted from the normal / * and - keys.
and thus I expect that x_set_keysym will not work because there
is no escape sequence to associate with something. That is why
I made changes to xkeys.c to make it work.

Regards, Thei.


On Sat, 28 Jan 2006, John E. Davis wrote:

> Thei Wijnen <t.wijnen@xxxxxxxxx> wrote:
> > I took Johns advice and used his edt.sl from jedsoft.org/test and
> > after another modification I got it working on windows and linux.
>
> Thanks for testing edt.sl and reporting your results.  However, I do
> not understand why changes to edt.sl were necessary.  In your
> windows jed.rc, simply using
>
>   NUMLOCK_IS_GOLD = 1;
>   require ("edt");
>
> *should* result in Key_Gold being set to "\eOP", which the NumLock key
> should generate.  Are you saying that this does not work?
>
> On Unix, if you want some other key to mimick the gold key, e.g.,
> Ctrl-A, then using
>
>   variable Key_Gold = "^A";
>   require ("edt");
>
> should work.  If this does not work, then something is wrong.
>
> > There is one problem however with the keypad keys '/' '*' and '-'.
> > The characters get inserted in the buffer in stead of doing the
> > functions that are defined by the (VT220) keys PF2, PF3 and PF4.
> >
> > I looked in the source code and found that these keys simply do not
> > generate the right escape sequence (like defined by VT220). I made
> > a change in the code, recompiled xjed and voila: xjed works and
> > these keys behave exactly the same as jed on Windows!
>
> There should be no need to recompile xjed to get these keys to
> generate specific escape sequences.  The x_set_keysym function can be
> used to associate a particular escape sequence with a keysym.
> Starting xjed via
>
>   xjed -l keycode -f keycode
>
> can be used to find the keysym associated with a key.
>
> Am I missing something?
>
> Thanks,
> --John
>
> --------------------------
> To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
> the word "unsubscribe" in the message body.
> Need help? Email <jed-users-owner@xxxxxxxxxxx>.

--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.