Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Salvador Mirzo Newsgroups: comp.unix.questions Subject: Re: xterm rlwrap sbcl Date: Fri, 13 Dec 2024 20:40:46 -0300 Organization: A noiseless patient Spider Lines: 155 Message-ID: <87a5czgni9.fsf@example.com> References: <87frmtofu3.fsf@example.com> <874j383n8h.fsf@example.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Sat, 14 Dec 2024 00:40:48 +0100 (CET) Injection-Info: dont-email.me; posting-host="389907832bffe20862f78b207653d4e2"; logging-data="3854757"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/9tnXRnVd4KacsHS0vIpPLnVMKXt8e34g=" Cancel-Lock: sha1:/y/Y4ftMwouhQezY3WAsIORCGEI= sha1:6dIPZ/KKGqonTHhGezrdL3kEHDk= Bytes: 5696 Paul writes: > On Thu, 12/12/2024 11:00 AM, Salvador Mirzo wrote: >> Paul 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 . >> >> 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 . 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 . 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.