Re: The ls command
- To: debian-user@lists.debian.org
- Subject: Re: The ls command
- From: Vincent Lefevre <vincent@vinc17.net>
- Date: Sat, 1 Nov 2025 11:59:38 +0100
- Message-id: <[🔎] 20251101105938.GB1128921@qaa.vinc17.org>
- Mail-followup-to: debian-user@lists.debian.org
- In-reply-to: <CAMPXz=qVAT2_nHOM8L8ZJqPJWpy7snzO=2q7dOsQdp_-QArOaw@mail.gmail.com>
- References: <20251031032606.GC957218@qaa.vinc17.org> <20251031034354.GK29520@wooledge.org> <CAMPXz=rUdJtvVRqLMtyuZyiJpuvNyAMxpkJt3Y7q5QsZbG0NKw@mail.gmail.com> <20251031133344.GA123970@cventin.lip.ens-lyon.fr> <aQS8sMMCSDOrnVf9@phare.normalesup.org> <CAPU_E+eT47-rzn+hAxFMeHawMLnX_wjwREMNHZj3t_bdQ+V=uQ@mail.gmail.com> <20251031174312.GB1029201@qaa.vinc17.org> <CAMPXz=pYo9UpwrvvqfL-USO3Lbb3a7LB-z=t=bSF8Gbx9UL57A@mail.gmail.com> <20251031215652.GP29520@wooledge.org> <CAMPXz=qVAT2_nHOM8L8ZJqPJWpy7snzO=2q7dOsQdp_-QArOaw@mail.gmail.com>
On 2025-10-31 22:31:01 +0000, David wrote:
> On Fri, 31 Oct 2025 at 22:04, Greg Wooledge <greg@wooledge.org> wrote:
> > It doesn't crash for me (on Trixie). It causes xterm to write some
> > information to the screen, and then 2 seconds go by, and then the
> > xterm closes cleanly (because no shell was requested).
>
> Oh thanks, sorry, I misused the word "crash", it didn't crash, it just
> closed the same as what you saw.
>
> I mistakenly assumed "crash" because of the context, and I didn't
> understand why until you explained. Thanks for pointing that out.
Hmm... I forgot that this depends on another config. You also need
to set reverseWrap (very useful in cooked mode). I've tested after
removing my default config:
$ xterm -k8 -xrm '*VT100.reverseWrap: true' -e 'printf "\x9a\x85\x08"; sleep 2'
Segmentation fault (core dumped)
$ echo $?
139
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
Reply to: