On Tue, 2020-08-18 at 12:06 +0100, Aaron Sloman wrote:
. . .
> SECOND step (for a bash user):
>
> source $usepop/pop/com/poplog.sh
>
> That will print out
> Poplog Version 16 (64 bit)
I believe I am doing that. Here is a snippet of my .bashrc file:
# Define $usepop and add Poplog paths to $PATH
usepop=/home/bill/Poplog/poplog/V16/poplog_base
source $usepop/pop/com/poplog.sh
And my .profile file sources .bashrc.
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.
. . .
> Anyhow, if you have not already done so please try:
>
> source $usepop/pop/com/poplog.sh
>
> Then try:
>
> pop11
> help rclib
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
Enter an alternative terminal type, or <RETURN> to abandon VED: linux
;;; HELP RCLIB not found - try HELP HELPFILES
;;; PRINT DOING
;;; DOING : popvedcommand pop_setpop_compiler
: bye
bill@debian-desktop:~$
I chose not to reset $TERM since earlier help on my problems indicated
what the fix was for the unknown terminal type -- use "linux" and I
wanted as clean a start as possible to show what is going on.
I'll keep your other tidbits for future explorations.
Thanks for your help,
Bill Wood
