Aaron Sloman See text for reply address wrote:
> I would propose (when I find time) to try
> to convert all the Ved key-binding files to work according to that
> standard, leaving the old configurations available for those who
> want them, in files with 'old' in their names.
That would be splendid, and also a lot of work. In the meantime, I
still think it would be a good idea - and not so much work - to put the
current Birmingham ncdxtermkeys files into the tar archive with your new
linuxterm.
> Another nasty problem.
...
> users now expect the backspace key to perform the vedchardelete
> function. Some also expect the Delete key to perform the veddotdelete
> function,
There's another one too. Ved is unique in my experience in using the
non-keypad arrow keys to go to the top, bottom, left and right of the
screen, instead of moving just one row or column. Anyone used to any
other editor - or even history mechanism - will keep tripping over that.
> I shall have to do some experimenting to find out what happens if
> that is turned off, so as to find out how the rest of the world has
> been experiencing Ved and XVed.
Right. I don't think new users can be expected to change their xterm X
defaults to accomodate ved.
> It would be useful if any Ved user reading this could check what
> keybindings they have for Ved and Xved for the function keys F1 to
> F12 (some of which do nothing on some terminals), and post them,
> specifying what terminal they are using, and on which machine
> and operating system poplog is running.
...
> The easiest way to get at the key bindings is to do
> ENTER hkey RETURN
The problem isn't just the binding of the escape sequences to ved
functions, but also the escape sequences themselves. There is a
document on xterm control sequences at
http://www.giccs.georgetown.edu/~ric/howto/Xterm-Title/ctlseqs.ps
that explains at least some of the possible range of variation among
programs calling themselves "xterm". The main thing seems to be the
first four function keys which might generate sequences beginning ESC O
or ESC [. A simple solution would be to map both sequences to the same
function as long as each xterm doesn't use the other's F1-F4 sequences
for some other key.
I've mentioned before that on several linux systems, I have to put Num
Lock on in order to get the correct keypad behaviour. You said you
hadn't seen that, but someone else (Jonathan Cunningham, I think)
reported that it happened to them too. I think that is a problem at the
x server level, as opposed to a variation among xterms, but I haven't
done a full investigation.
Steve
|