Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #16296

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

Path csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From worley@alum.mit.edu (Dale R. Worley)
Newsgroups gnu.bash.bug
Subject Re: CTRL-C on command line does not cancel current command
Date Sun, 10 May 2020 21:50:46 -0400
Lines 13
Approved bug-bash@gnu.org
Message-ID <mailman.2598.1589162343.3066.bug-bash@gnu.org> (permalink)
References <406707EB-FFAC-48BD-BA8F-37CFE09CFFB9@kelaita.com> <87h7wn44uh.fsf@hobgoblin.ariadne.com>
NNTP-Posting-Host lists.gnu.org
X-Trace usenet.stanford.edu 1589162343 1130 209.51.188.17 (11 May 2020 01:59:03 GMT)
X-Complaints-To action@cs.stanford.edu
Cc bug-bash@gnu.org
To Paul Kelaita <paul@kelaita.com>
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1589161848; bh=kAuZ9hHxd9FL9qBcbQPH8bXDiO/o6Qwq493WabtptgU=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=Keh7Z2Cl6iZ/fyl4mMUSzo4eq7fR0dwG+sC8TSHDTwsYe/6wxxsvfQkay/o1yt5iG FdZ+aFyEgXnS4jUFn0cBQFTePI6NQS7qB0lp8XrA73Q0zLF2gwFFFiTF6YOklcXAne uMpIWfy1oDjdP0Rbvz2CdI5j28XxAPhr0G+S4pnhXwXxch72qdeYsiticq67AUsXhh O+PyBdWmx8zA7qAfNjssfF9abLdxPMdCDfbpGdpfbhDNOyVUiCsioVoArcyx8yfh8r LVZhJ1foag7+6yBbbiPNXcAvkwbuhq6m2641sGd1qXrKy7Tmj6R+ZQC+5sBulO1det pudseA0145kuw==
X-Xfinity-VMeta sc=-100.00;st=legit
X-Authentication-Warning hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
In-Reply-To <406707EB-FFAC-48BD-BA8F-37CFE09CFFB9@kelaita.com> (paul@kelaita.com)
Received-SPF permerror client-ip=2001:558:fe21:29:69:252:207:35; envelope-from=worley@alum.mit.edu; helo=resqmta-ch2-03v.sys.comcast.net
X-detected-operating-system by eggs.gnu.org: First seen = 2020/05/10 21:50:48
X-ACL-Warn Detected OS = ???
X-Spam_score_int -25
X-Spam_score -2.6
X-Spam_bar --
X-Spam_report (-2.6 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN
X-Spam_action no action
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <87h7wn44uh.fsf@hobgoblin.ariadne.com>
Xref csiph.com gnu.bash.bug:16296

Show key headers only | View raw


Paul Kelaita <paul@kelaita.com> writes:
> Sorry, I'm wondering if I should have taken this to the iSH forums,
> but it just seems like a bash issue.

You should ask around, because how Ctrl-C cancels input involves the
interaction of the OS, the bash code proper, and (I assume) the stdin
library.  E.g. if the OS doesn't actually deliver the characters to bash
until you type RET, then the OS has to take care of clearing the
partially-input line.  And all of these actions can be modulated by your
stty settings and any special input mode(s) that bash activates.

Dale

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Re: CTRL-C on command line does not cancel current command worley@alum.mit.edu (Dale R. Worley) - 2020-05-10 21:50 -0400

csiph-web