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

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