On Mon, 2020-08-17 at 14:28 -0400, [email protected] wrote: . . . > When I give the 'ved' command from an "unknown terminal type", I > get, > along with "Unknown terminal type:<termtype>", an invitation > > Enter an alternative terminal type, or <RETURN> to abandon VED > > Entering 'linux' as a terminal type, then gets me a ved session. Do > you > not get that second line? If you do, I would suggest trying 'linux' > as > your terminal type. An alternative would be setting > > export TERM=linux > > before giving the ved command. That might work if you don't get the > "Enter an alternative" invitation.
Yes, I get the invitation. Using either "linux" or "xterm" seems to fix that problem. > Are you by any chance giving the TEACH TEACHFILES command literally, > in > upper case? If so, try lower case. The upper case is a convention > for > making commands stand out in teach files, but of course you have no > way > of knowing that without access to the teach files. I tried it both uppercase and lowercase with no difference. > If you are able to run pop11, clisp, etc., you probably have the > environment variable $usepop set. Do you have the file > $usepop/pop/teach/teachfiles in your installation? That's what you > are > trying to read with ved, but you can read it with a different editor, > or > with more or less, if you can't get ved to work. Yes, the file is there. I was just trying to do some simple things in the "veduserguide"; after poking around the dir tree I found the "teach" dir and opened up "teachfiles" in emacs; no problem. . . . > $usepop/pop/lib/ved/term/vedextermkeys.p and > $usepop/pop/lib/ved/term/vedlinuxkeys.p Found 'em, thanks. The main problem now seems to be that an attempt to use any of the REF, DOC, HELP or TEACH commands fails with the "not found" error. Thanks for your help, Bill Wood
