Date: Sat, 1 Nov 2025 22:44:54 -0600 From: Warner Losh <imp@bsdimp.com> To: Dennis Clarke <dclarke@blastwave.org> Cc: freebsd-current@freebsd.org Subject: Re: a really big question : why not "^C" for a CTRL-C with default /bin/sh ? Message-ID: <CANCZdfrWwHyqv36_Z5H5fvemve26PAuaUMYckrmHjUQk7H09mQ@mail.gmail.com> In-Reply-To: <0c09c6fa-7071-4119-b97e-fc6d83f9fc3f@blastwave.org> References: <f5929936-1184-46e6-929b-72fe460719aa@blastwave.org> <864EE1FC-1533-47D4-A395-C24F25269EE0@freebsd.org> <342c6a91-a8a1-483d-861e-8e8c6d79998f@blastwave.org> <9ea41e44-7160-40eb-9d80-b8bf13a7f396@mm.st> <0c09c6fa-7071-4119-b97e-fc6d83f9fc3f@blastwave.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sat, Nov 1, 2025 at 7:49 PM Dennis Clarke <dclarke@blastwave.org> wrote: > On 11/1/25 21:22, cyric@mm.st wrote: > > Dennis Clarke wrote: > >> On 11/1/25 20:30, Michael Gmelin wrote: > >>> > >>> > >>>> On 2. Nov 2025, at 00:34, Dennis Clarke <dclarke@blastwave.org> > wrote: > >>>> > >>>> > >>>> This is about as annoying as a small sharp stone stuck in a shoe : > >>>> > >> ... > >>> Wasn‘t this always the default behavior in /bin/sh? > >>> > >> > >> If it was and if it is then it is broken and always has been. > >> > >> No UNIX shell *ever* behaves this way in at least the last four decades. > > > > zsh does, ksh93 (illumos) does. > > > > Those both hide the CTRL-C "^C" chars ? > > Oracle Solaris 11.4.81.193.1 Assembled April 2025 > n$ > n$ uname -a > SunOS neptune 5.11 11.4.81.193.1 sun4v sparc sun4v non-virtualized > n$ echo $SHELL > /usr/xpg4/bin/sh > n$ > n$ ls la la la la la ^C > n$ > n$ which ksh93 > /usr/bin/ksh93 > n$ > n$ ksh93 > dclarke@neptune:~$ > dclarke@neptune:~$ and then we have Dave Korn > dclarke@neptune:~$ well look ... no CTRL-C ^C chars ? > > dclarke@neptune:~$ > > Nice one. I did not recall the ksh93 issue. Must be something in the > stty options being set or unset. > tcsh doesn't report it at the prompt (most likely because libedit is in play), but does if you type cat<return> and then ^C. Warner [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sat, Nov 1, 2025 at 7:49 PM Dennis Clarke <<a href="mailto:dclarke@blastwave.org">dclarke@blastwave.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 11/1/25 21:22, <a href="mailto:cyric@mm.st" target="_blank">cyric@mm.st</a> wrote:<br> > Dennis Clarke wrote:<br> >> On 11/1/25 20:30, Michael Gmelin wrote:<br> >>><br> >>><br> >>>> On 2. Nov 2025, at 00:34, Dennis Clarke <<a href="mailto:dclarke@blastwave.org" target="_blank">dclarke@blastwave.org</a>> wrote:<br> >>>><br> >>>> <br> >>>> This is about as annoying as a small sharp stone stuck in a shoe :<br> >>>><br> >> ...<br> >>> Wasn‘t this always the default behavior in /bin/sh?<br> >>><br> >><br> >> If it was and if it is then it is broken and always has been.<br> >><br> >> No UNIX shell *ever* behaves this way in at least the last four decades.<br> > <br> > zsh does, ksh93 (illumos) does.<br> > <br> <br> Those both hide the CTRL-C "^C" chars ?<br> <br> Oracle Solaris 11.4.81.193.1 Assembled April 2025<br> n$<br> n$ uname -a<br> SunOS neptune 5.11 11.4.81.193.1 sun4v sparc sun4v non-virtualized<br> n$ echo $SHELL<br> /usr/xpg4/bin/sh<br> n$<br> n$ ls la la la la la ^C<br> n$<br> n$ which ksh93<br> /usr/bin/ksh93<br> n$<br> n$ ksh93<br> dclarke@neptune:~$<br> dclarke@neptune:~$ and then we have Dave Korn<br> dclarke@neptune:~$ well look ... no CTRL-C ^C chars ? <br> <br> dclarke@neptune:~$<br> <br> Nice one. I did not recall the ksh93 issue. Must be something in the <br> stty options being set or unset.<br></blockquote><div><br></div><div>tcsh doesn't report it at the prompt (most likely because libedit is in play), but does if you type cat<return> and then ^C.</div><div><br></div><div>Warner</div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrWwHyqv36_Z5H5fvemve26PAuaUMYckrmHjUQk7H09mQ>