Stephen Isard <S.IsardDeleteThis@ed.ac.uk> writes:
> Date: Mon, 05 Mar 2001 16:30:34 +0000
> Organization: HCRC or CCS, University of Edinburgh
>
> If you start ved (not xved) from the command line in an xterm window
> under this version of linux (and I think it will be the same in many
> others) ved reads the value 'xterm' from the TERM environment variable
....
I have been using it in RedHat 6.1 on a Dell Laptop, and have just
looked and discovered that in my vedinit.p file I have the following:
vedset keys
;;; Stuff for linux Xterms (overrides vedvt100keys.p defaults)
"marklo" = '\^[OP'
"markhi" = '\^[OQ'
"clearhead" = '\^[OR'
"linedelete" = '\^[OS'
endvedset
;;; the last two should also have entries for ved_yankw and ved_yankl
;;; when preceded by ESC.
I also found this:
if systranslate('LINUX') then
vedset keys
;;; Stuff for linux console
"marklo" = '\^[[[A'
"markhi" = '\^[[[B'
"clearhead" = '\^[[[C'
"deleteline" = '\^[[[D'
"cleartail" = '\^[[[E'
"enter" = '\^[[1~'
"topfile" = '\^[[2~'
"chardelete" = '\^[[3~'
"endfile" = '\^[[4~'
endvedset;
endif;
I can't rememember when I put all that there. I don't think that's
included in anything I have packed into the linux poplog distribution,
nor in anything in the local sussex libraries. It looks as if I should
at least put the first bit into lib vedncdxtermkeys, possibly guarded
by a test for linux?
> However, ncdxtermkeys expects the function keys F1-F4 to
> generate sequences beginning "esc [ 1", like the rest of the function
> keys, whereas in xterm version 3.3.3.1(88), they actually generate
> "esc 0 P" through "esc 0 S". UNLESS, that is, you have set
> *VT100*oldXtermFKeys: true
> in an app-defaults or Xdefaults file somewhere. (Well of course you
> will have done that, won't you?) The xterm man page doesn't actually
> explain what is old and what is new, but the name of the resource looked
> suspicious, so I tried it and it worked. Presumably, it will mess up
> some other program that uses the function keys inside an xterm window
> though.
It sounds as if changing Ved's default key bindings is better.
> I've also found that in order for ved to use the keypad keys, I have to
> set numlock on
I have never seen that.
> If we want potential new users to try out poplog, it's important that
> they have a working ved with which to read the documentation, and they
> can't be expected to disrupt their existing environments to get one.
> So ved has to be as robust as possible against unfamiliar terminal
> behaviour. That would suggest to me that, in the absence of an explicit
> override, it should look at termcap/terminfo entries first, rather than
> as a fallback when there is no named file for the TERM terminal type.
> However, the situation described above shows that termcap can't always
> be relied on either. Is there a way of checking for what the F1 key
> actually generates, apart from asking the user to press it?
There is a program written by Steve Leach that attempts to generate a
complete table of key bindings and prints them out. You can fetch it
from
http://www.cs.bham.ac.uk/research/poplog/auto/ved_keymap.p
It makes use of vednormaltable and vedescapetable which are used to
store keybindings. Unfortunately it can only tell you want Ved
procedures various control and escape sequences map onto.
Finding out which keys generate those sequences may require
interrogating the user.
Maybe a new user should be asked to press all the function keys in turn,
and a record of the bindings made in a file, or two files: one for when
Ved is used, and one for Xved.
Incidentally in an Xterm I use LIB vedxgotomouse, which is often useful.
That means that to get the standard Xterm mouse behaviour you have to
press Shift. I've got used to that. An alternative is to use different
xterm windows for Ved and for other things.
Aaron
>
> Maybe the answer is to make xved be the default version of ved when you
> are inside X? But it is noticeably slower to start up on a 400MHz
> Celeron, to say nothing of my poor old Sun Ultra at work, and there are
> issues of motif or not.
I find that with the standard Birmingham startup.psv Xved starts up
almost as quickly on a 400 mhz Dell laptop as Ved. I just prefer not
having a multi-window editor most of the time.
> Personally, I find plain ved in a linux console
> window just great - big, easy to read characters and lightning fast.
> But somehow I don't think it is going to have universal appeal.
You can set your xterm font size bigger than the default when you create
the xterm window. I use 10x20 most of the time, though on a lower
resolution screen (i.e. with fewer pixels) I go for smaller fonts to
avoid problems of space on the screen.
Aaron
====
Aaron Sloman, ( http://www.cs.bham.ac.uk/~axs/ )
School of Computer Science, The University of Birmingham, B15 2TT, UK
EMAIL A.Sloman AT cs.bham.ac.uk (ReadATas@please !)
PAPERS: http://www.cs.bham.ac.uk/research/cogaff/
FREE TOOLS: http://www.cs.bham.ac.uk/research/poplog/freepoplog.html
|