[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CTRL-C on command line does not cancel current command

From: Paul Kelaita
Subject: Re: CTRL-C on command line does not cancel current command
Date: Fri, 8 May 2020 14:46:45 -0700

Oh, it’s definitely bash.  Works nicely in iSH.  Sorry, I’m wondering if I 
should have taken this to the iSH forums, but it just seems like a bash issue.  
I can run sh, csh, tcsh, and they all handle CTRL-C fine on the command line.  
INTR is correct (see below), I’ve tried ‘stty sane’ and ‘stty reset’ to no 

I know it’s such a minor issue, but it’s one of those that keeps biting me 
throughout the day because of the way I’m trained.  I realize I can use CTRL-U, 

Anyway, here is a snapshot of what you were asking.  I haven’t used readline 
much, if at all.


TERMCAP=SC|screen|VT 100/ANSI X3.64 virtual terminal:\

speed 0 baud; rows 63; columns 161; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd -cmspar cs5 -hupcl -cstopb -cread -clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany -imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok echonl -noflsh -xcase -tostop -echoprt
echoctl -echoke -flusho -extproc

GNU bash, version 5.0.11(1)-release (i586-alpine-linux-musl)
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

> On May 8, 2020, at 2:36 PM, Greg Wooledge <address@hidden> wrote:
> On Fri, May 08, 2020 at 02:26:34PM -0700, Paul Kelaita wrote:
>> Only seeing this on Alpine BusyBox (iSH) on iOS 13.x with either 5.0.11 or 
>> 5.0.17
> Busybox is a shell, in addition to being other tools.  Perhaps you're
> not even in bash at all?
> What does "ps -p $$" say?  How about "set | grep BASH"?
> If it turns out that you really are in bash, not in busybox, then we'd
> need to know a bit more about your environment.  What kind of terminal
> emulator are you in?  What does "stty -a" say?  Have you configured
> readline (look for /etc/inputrc and ~/.inputrc files) in some nonstandard
> way?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]