Date: Sat, 1 Nov 2025 20:59:55 -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: <342c6a91-a8a1-483d-861e-8e8c6d79998f@blastwave.org> In-Reply-To: <864EE1FC-1533-47D4-A395-C24F25269EE0@freebsd.org> References: <f5929936-1184-46e6-929b-72fe460719aa@blastwave.org> <864EE1FC-1533-47D4-A395-C24F25269EE0@freebsd.org>
index | next in thread | previous in thread | raw e-mail
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. Perhaps three decades. As far back as I can recall and that includes using paper terminals. It may be the libedit library there has a borked way of dealing with a SIGINT. -- -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spokenhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?342c6a91-a8a1-483d-861e-8e8c6d79998f>