Re: a really big question : why not "^C" for a CTRL-C with default /bin/sh ?

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.

> 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.