On Tue 18 Feb 2020 at 02:34, Aaron Sloman <[email protected]>
wrote:

Andreas wrote:

I don't know enough about poplog to add jmuch of value here,
but
maybe you have a different readline in your image? Probably
there is
emacsreadline linked in?
Just a wild guess.

[Apologies for delayed acknowledgement.]

It's not possible. The colon in the command line:

 pop11 :"readline()=>1 + 1"

or, equivalently,

 pop11 ":readline()=>1 + 1"

tells pop11 that it has to treat the quoted string as pop11
code, exactly
as if it had been typed in after pop11 started up -- except for
some
setup differences due to occurring in the command line.

To invoke something outside poplog you'd need sysobey, e.g.

: sysobey('date');
Tue 18 Feb 01:27:18 GMT 2020

Anyhow, there's no readline in my $PATH that could be picked up
in error.
And there's no emacs within poplog unless you explicitly use
Brian Logan's
emacs addon, provided for people who don't want to learn to use
Ved.

        $usepop/pop/packages/emacs

Which I don't use: ved is now burnt into my brain (though age is
producing
gaps...)

Oh, I do understand that :-)

I was talking about the emacsreadline in
'pop/lib/lib/emacsreadline.p'.
It is linked into the image in e.g. 'pop/com/mkstartup.bham'.
I was just suggesting this might be the source of differernt
behaviour.

Andreas

--
ceterum censeo redmondinem esse delendam

Reply via email to