| Deutsch English Français Italiano |
|
<vm1hk4$1etjc$4@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Bozo User <anthk@disroot.org> Newsgroups: comp.unix.questions Subject: Re: xterm rlwrap sbcl Date: Sun, 12 Jan 2025 23:01:24 -0000 (UTC) Organization: A noiseless patient Spider Lines: 49 Message-ID: <vm1hk4$1etjc$4@dont-email.me> References: <87frmtofu3.fsf@example.com> Injection-Date: Mon, 13 Jan 2025 00:01:25 +0100 (CET) Injection-Info: dont-email.me; posting-host="0d769781d0c9f62b1fc94ca3a2e1f783"; logging-data="1537644"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18HerbH25odlVC9yIySNUYU" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:qVzfA8gCgT0c/bD8vr/TgDCKA4U= Bytes: 2194 On 2024-12-12, 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. > > When I invoke ``rlwrap sbcl'', I get a little bug: > > --8<-------------------------------------------------------->8--- > $ 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 > --8<-------------------------------------------------------->8--- > > Of course, I typed > > (format t "hello~%") > > but we end up seeing > > (f(format t "hello~%") > > If I type > > (write-string "hello") > > we end up with > > * (w(write-string "hello") > hello > "hello" > > You get the idea. This doesn't happen with other programs. It seems to > be something specific to sbcl, though I could hardly believe that sbcl > is guilty of anything here. > > Any remedies? You can try using vim+slimv, it's much better than a simple REPL