unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>, 30937@debbugs.gnu.org
Subject: bug#30937: In `comment-region', C-g doesn't work.
Date: Sun, 25 Mar 2018 20:43:15 +0200	[thread overview]
Message-ID: <87po3s6loc.fsf@linux-m68k.org> (raw)
In-Reply-To: <83tvt4f2oc.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 25 Mar 2018 21:08:51 +0300")

On Mär 25 2018, Eli Zaretskii <eliz@gnu.org> wrote:

> comment-region doesn't need to test that explicitly, it is tested in
> many underlying primitives.  Moreover, on a TTY, C-g triggers a
> SIGINT, which should cause a throw to top-level even if quit-flag is
> not tested, just because it's a signal.

SIGINT only sets quit-flag.  If you want it to take effect you need to
call maybe_quit.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."





  reply	other threads:[~2018-03-25 18:43 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
2018-03-25 18:08         ` Eli Zaretskii
2018-03-25 18:43           ` Andreas Schwab [this message]
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=87po3s6loc.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=30937@debbugs.gnu.org \
    --cc=acm@muc.de \
    --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).