Date: Sat, 1 Nov 2025 19:33:33 -0400 From: Dennis Clarke <dclarke@blastwave.org> To: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: a really big question : why not "^C" for a CTRL-C with default /bin/sh ? Message-ID: <f5929936-1184-46e6-929b-72fe460719aa@blastwave.org>
index | next in thread | raw e-mail
This is about as annoying as a small sharp stone stuck in a shoe :
h# uname -apKU
FreeBSD hydra 15.0-BETA4 FreeBSD 15.0-BETA4
releng/15.0-n280841-a7707f2a3bf4 GENERIC amd64 amd64 1500068 1500068
h#
h# echo $SHELL
/bin/sh
h# ldd /bin/sh
/bin/sh:
libedit.so.8 => /lib/libedit.so.8 (0x3bf400ba2000)
libc.so.7 => /lib/libc.so.7 (0x3bf403255000)
libtinfow.so.9 => /lib/libtinfow.so.9 (0x3bf404396000)
libsys.so.7 => /lib/libsys.so.7 (0x3bf404618000)
[vdso] (0x3bf400941000)
h#
However I can type in anything and hit CTRL-C and never ever see the
much needed "^C" chars on the input line :
h# zpool destroy -f zroot
h#
Well there you have it. Can you see the time I hit CTRL-C ? No?
Neither can I.
This is a really annoying "feature" in the default shell.
There must be a way to fix this weird behavior.
--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f5929936-1184-46e6-929b-72fe460719aa>