Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Salvador Mirzo <smirzo@example.com>
Newsgroups: comp.unix.questions
Subject: Re: xterm rlwrap sbcl
Date: Fri, 13 Dec 2024 20:59:25 -0300
Organization: A noiseless patient Spider
Lines: 62
Message-ID: <87o71ff82q.fsf@example.com>
References: <87frmtofu3.fsf@example.com> <eli$2412122205@qaz.wtf>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Sat, 14 Dec 2024 00:59:27 +0100 (CET)
Injection-Info: dont-email.me; posting-host="389907832bffe20862f78b207653d4e2";
	logging-data="3854757"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18m0iEuf8u3h+PFQZpFktJRo67RFlrjpSs="
Cancel-Lock: sha1:Qd2l7DrfGNTLQ2M8zQA7QWGV6mQ=
	sha1:HcWcaMVz6rqWDu1UuafpagB7gcM=
Bytes: 3272

Eli the Bearded <*@eli.users.panix.com> writes:

> In comp.unix.questions, Salvador Mirzo  <smirzo@example.com> wrote:
>> I know next to nothing about terminals.  My .profile says TERM=xterm.
>> 
>> $ echo $TERM
>> xterm
>> 
>> I really am running PuTTY on Windows and logging in to a FreeBSD system.
>
> It sounds to me like the terminal definition (terminfo or termcap as
> appropriate to FreeBSD) disagrees with the terminal implementation
> (Putty here). This is a not uncommon thing to happen.
>
> I would first see if there are Putty preferences that fix this.

My trial-and-error was to set local echo to ``force off'' and local line
editing to ``force off'':

  https://prnt.sc/e6SedO_IiHTX

No difference.  (I also set the terminal-type string to vt100.)

I just installed the terminal Alacritty.  I see the same behavior on it:

$ echo $TERM
xterm-256color

$ uname -a
FreeBSD my.domain 14.1-RELEASE-p5 FreeBSD 14.1-RELEASE-p5 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
*

> Second see if it could be fixed with an intermediary that grabs terminal
> output from the shell programs and rewrites before it gets to Putty.
> Tools like tmux or screen will do that.
>
> Third I'd try to fix the terminal definition. Using script to capture
> the output of the terminal programs with all terminal escape codes
> intact, I'd examine that output to look for cause of the bad formatting
> and then search the terminal definition (terminfo or termcap) for the
> terminal "capability" that causes the issue and fix or remove it.
>
> Most capabilities are "nice to haves" instead of "required" so just
> removing them doesn't break things. But editing those definitions is
> not for the faint of heart. That's why the intermediary programs
> rewriting things "works".

That's more technical than I could do right now on my own.  If you have
the energy describe what it is that I must do in more details---what
software to use et cetera---I will do it.  Thanks!