Date: Sat, 1 Nov 2025 21:48:56 -0400 From: Dennis Clarke <dclarke@blastwave.org> To: freebsd-current@freebsd.org Subject: Re: a really big question : why not "^C" for a CTRL-C with default /bin/sh ? Message-ID: <0c09c6fa-7071-4119-b97e-fc6d83f9fc3f@blastwave.org> In-Reply-To: <9ea41e44-7160-40eb-9d80-b8bf13a7f396@mm.st> 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>
index | next in thread | previous in thread | raw e-mail
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. -- -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spokenhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0c09c6fa-7071-4119-b97e-fc6d83f9fc3f>