Re: xterm rlwrap sbcl

On Fri, 12/13/2024 6:49 PM, Salvador Mirzo wrote:

Salvador Mirzo <smirzo@example.com> writes:
 

Paul <nospam@needed.invalid> writes:
>

On Thu, 12/12/2024 11:00 AM, Salvador Mirzo wrote:

Paul <nospam@needed.invalid> writes:
>

On Thu, 12/12/2024 1:05 AM, Lawrence D'Oliveiro wrote:

On Wed, 11 Dec 2024 22:22:28 -0300, Salvador Mirzo wrote:
>

$ echo $TERM
xterm

>
Same here.
>

I really am running PuTTY on Windows and logging in to a FreeBSD system.

>
I am running KDE Konsole on Linux to access a local shell.
>

Of course, I typed
>
  (format t "hello~%")
>
but we end up seeing
>
  (f(format t "hello~%")

>
My terminal window shows:
>
    * (format t "hello~%")
    hello
    NIL
>

If I type
>
  (write-string "hello")
>
we end up with
>
* (w(write-string "hello")
hello
"hello"

>
My terminal window shows:
>
    * (write-string "hello")
    hello
    "hello"
>
Most likely suspect: Windows is the weakest link.
>

>
This is the easiest thing I could wire up as a simulation
for those at home. Since I don't know a thing about LISP,
I can't very well address that part of the problem.
>
   [Picture]
>
    https://i.postimg.cc/9FVtm0S5/putty-ssh-session-overview.gif
>
The $TERM declaration and the color capability,
don't exactly match in my copy of PuTTY. The distortion
seen by the OP does not look like wrongly emitted
color codes, which could make more of a mess.
PuTTY is not declaring "xterm-256color" as the term type.
>
   [Picture]
>
    https://i.postimg.cc/QMtZRXsc/putty-settings.gif

>
I believe this is a FreeBSD thing.  Using the same PuTTY and the same
Windows, but loging in on a GNU Debian system, I don't see any problems:
>
--8<-------------------------------------------------------->8---
%uname -a
Linux kontesti.me 6.2.9-x86_64-linode160 #1 SMP PREEMPT_DYNAMIC Wed
Apr 5 15:30:32 EDT 2023 x86_64 GNU/Linux
%sbcl --version
>
SBCL 1.2.4.debian
%echo $TERM
xterm
>
%rlwrap sbcl
This is SBCL 1.2.4.debian, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.
>
SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
* (format t "hello~%")
hello
NIL
--8<-------------------------------------------------------->8---
>

>
I set up a FreeBSD 14.2 VM and at least in terms of termcap,
and $TERM ("xterm"), the results so far look the same as with
my attempt on Linux Mint VM.
>
The contents of the prompt definition on the freebsd account are the default:
>
$TERM   "xterm"
$PS1    \u@\h:\w \$
>
And I doubt a locale definition could make that sort of pattern.
It sorta looks like a terminal "echo" problem but why does it only
happen for the first few characters of a line ?

>
Hey, I also have a FreeBSD 14.2, but I also have a FreeBSD 14.1.  It
turns out the problem does not happen on the FreeBSD 14.2:
>
$ echo $TERM
xterm
>
$ uname -a
FreeBSD b 14.2-RC1 FreeBSD 14.2-RC1 releng/14.2-n269505-5395ddd7aa13
GENERIC amd64
>
$ sbcl
This is SBCL 2.4.9, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.
>
SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
* (format t "hello~%")
hello
NIL
*
>
But, as you know already, here's what happens on FreeBSD 14.1:
>
$ echo $TERM
xterm
>
$ uname -a
FreeBSD my.domain 14.1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 GENERIC amd64
>
$ sbcl
This is SBCL 2.4.9, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.
>
SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
* (format t "hello~%")
hello
NIL
*
>
What?  It stopped doing it.  What in the world is going on?  This was
not a on-and-off thing; it was always doing it.  I did not even set
anything new on my PuTTY configuration or anything.  I'm very puzzled
now.

 
Sorry!  I forgot I have to use rlwrap.  So the problem is related to the
rlwrap then.  That was not clear to me yet.  So, with rlwrap I see the
behavior on both FreeBSD 14.1 and 14.2:
 
$ uname -a
FreeBSD b 14.2-RC1 FreeBSD 14.2-RC1 releng/14.2-n269505-5395ddd7aa13 GENERIC amd64
 
$ rlwrap sbcl
This is SBCL 2.4.9, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.
 
SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
* (f(format t "hello~%")
hello
NIL
*
 
Same thing on FreeBSD 14.1.  (So, make sure you're using rlwrap.)
 
Someone (maybe you) suggested I should change my PuTTY terminal-type
string to vt100.  I did.  Same result:
 
$ uname -a
FreeBSD my.domain 14.1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 GENERIC amd64
 
$ echo $TERM
vt100
 
$ rlwrap sbcl
This is SBCL 2.4.9, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.
 
SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses.  See the CREDITS and COPYING files in the
distribution for more information.
* (f(format t "hello~%")
hello
NIL
 

The pattern is not suggestive of a $TERM problem, but it was
worth trying a change anyway.

Perhaps the rlwrap developer recognizes the pattern ?

   Paul