Bill,
You have raised different problems at different times. I don't think this
one, concerned with terminal type, was addressed in any of my previous
messages, though I know you have received a partial answer.
Your recent message:
[BW]
> ....
> As evidence here is the result of kicking off a new xterm:
>
> Poplog?Version 16 (64 bit)
> bill@debian-desktop:~$?
>
> Notice that the "Poplog Poplog?Version 16 (64 bit)" message does appear
> at start up.
> . . .
Yes that's fine.
[AS]
> > Anyhow, if you have not already done so please try:
> >
> > ????source $usepop/pop/com/poplog.sh
> >
> > Then try:
> >
> > ????pop11
> > ????help rclib
[BW]
> Again, starting up a fresh xterm:
>
> Poplog Version 16 (64 bit)
> bill@debian-desktop:~$ pop11
>
> Sussex Poplog (Version 16.0 Sun Aug 16 18:54:52 CDT 2020)
> Copyright (c) 1982-1999 University of Sussex. All rights reserved.
>
> Setpop
> : help rclib
> Unknown terminal type: xterm-256color
That suggests that your value of $TERM at the time when you start poplog is
xterm-256-color. That's not recognized by poplog, and is not detected when
you source poplog.sh
See HELP TERMINAL [ i.e. the file: $usepop/pop/help/terminal ]
which states, among other things:
A list of terminal libraries is given in REF * VEDTERMINALS.
i.e. the file: $usepop/pop/ref/vedterminals
As a short term alternative you can define a command to set $TERM to be xterm
and then run pop11.
You can also include instructions to be run when pop11 starts up.
I've discovered this is in my $poplib/init.p file
;;; Handle rxvt type terminals like xterms
lvars TERM = systranslate('TERM');
if member(TERM, ['rxvt' 'urxvt' 'rxvt-unicode' 'rxvt-unicode-256color'])
then
'xterm' -> systranslate('TERM')
endif;
That tells pop11 and Ved to treat all of those terminals as if they were of
type 'xterm'. (I suspect they all have supersets of xterm functionality.)
I don't remember inserting it. It must have been many years ago!
(I don't know why I put it into init.p rather than vedinit.p)
You can use that mechanism to tell pop11 to treat xterm-256-color as
equivalent to xterm, e.g. in your own directory $poplib, in a file called
vedinit.p or init.p
Try copying anything you think important in
$usepop/pop/packages/setup/Poplib/vedinit.p
$usepop/pop/x/ved/lib/vedxvedinit.p
into your version of $poplib/vedinit.p
It can also include an init.p file for more general pop11 initialisation
of your own environment -- with similar facilities for the other poplog
languages.
[Incidentally, the vedinit.p file in the packages library, will not be in
Waldek's github setup, but the second file is, because he understandably
chose to focus on getting the core of 64bit linux poplog to work properly
-- which is why I had to set up a mechanism for combining his version with
the omitted stuff to enable experienced poplog users to work in the
environment they are familiar with.]
I was surprised to learn from Steve Isard's recent message that 'linux' is
one of the values for $TERM that works for poplog. I am doubly surprised
because different terminal types with different interaction requirements,
for which different settings are needed, can be used on linux. So, in
principle, 'linux' should *not* determine a terminal type. But I have
checked that it works for me though I don't know why!]
I'll return to other issues later.
Aaron
