From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30937@debbugs.gnu.org
Subject: bug#30937: In `comment-region', C-g doesn't work.
Date: Sun, 25 Mar 2018 17:15:10 +0000 [thread overview]
Message-ID: <20180325171510.GD6292@ACM> (raw)
In-Reply-To: <831sg8gkzj.fsf@gnu.org>
Hello, Eli.
On Sun, Mar 25, 2018 at 19:48:00 +0300, Eli Zaretskii wrote:
> > Date: Sun, 25 Mar 2018 15:39:59 +0000
> > Cc: 30937@debbugs.gnu.org
> > From: Alan Mackenzie <acm@muc.de>
> > Yes, I've just tried it on X. It works there (except it leaves point in
> > a suboptimal position: the starting point. It should really leave point
> > after the last newly commented line when the quit happened). It works
> > on emacs -nw, with the same proviso.
> > It doesn't work at all on a Linux tty.
> ??? How come it works in "emacs -nw" but not on a "Linux tty" (which
> is what, btw? the raw Linux console?).
Yes, the raw Linux console. I don't know why it doesn't work, here.
> In both cases, C-g should trigger a SIGINT, so Emacs should be even
> more responsive to C-g than on X.
For what it's worth, quit-flag is getting set on a C-g (I hacked up my
own quit mechanism to test this). It would appear that nothing is
testing quit-flag during the comment-region.
> What am I missing?
I honestly don't know.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-03-25 17:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 14:28 bug#30937: In `comment-region', C-g doesn't work Alan Mackenzie
2018-03-25 15:32 ` Eli Zaretskii
2018-03-25 15:39 ` Alan Mackenzie
2018-03-25 16:48 ` Eli Zaretskii
2018-03-25 17:15 ` Alan Mackenzie [this message]
2018-03-25 18:08 ` Eli Zaretskii
2018-03-25 18:43 ` Andreas Schwab
2018-03-25 19:14 ` Eli Zaretskii
2018-03-25 21:08 ` Andreas Schwab
2018-03-25 17:35 ` Ivan Shmakov
2018-03-25 18:11 ` Eli Zaretskii
2018-03-31 14:21 ` Noam Postavsky
2019-01-09 1:06 ` Glenn Morris
2019-01-10 11:21 ` Alan Mackenzie
2019-11-02 0:53 ` Stefan Kangas
2018-03-25 16:07 ` Andreas Schwab
2018-03-25 16:01 ` Alan Mackenzie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180325171510.GD6292@ACM \
--to=acm@muc.de \
--cc=30937@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).