From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 1392ec7 2/3: A quicker check for quit
Date: Thu, 26 Jan 2017 22:02:09 +0200 [thread overview]
Message-ID: <83ziid1tfi.fsf@gnu.org> (raw)
In-Reply-To: <fce04695-69d9-9dcb-5774-79879236f742@cs.ucla.edu> (message from Paul Eggert on Thu, 26 Jan 2017 09:45:09 -0800)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Thu, 26 Jan 2017 09:45:09 -0800
>
> This leads me to wonder: what's the point of immediate_quit? If
> immediate_quit doesn't always cause C-g to immediately quit, why are we
> bothering with an immediate_quit variable?
It's only tested in the TTY input code, AFAIK.
> Or if immediate_quit makes sense, then should we arrange for a C-g
> under X to behave more like C-g on a terminal, and do a longjmp?
I hope not.
next prev parent reply other threads:[~2017-01-26 20:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170126052541.29089.5382@vcs.savannah.gnu.org>
[not found] ` <20170126052542.828422201BC@vcs.savannah.gnu.org>
2017-01-26 13:40 ` [Emacs-diffs] master 1392ec7 2/3: A quicker check for quit Stefan Monnier
2017-01-26 17:45 ` Paul Eggert
2017-01-26 20:02 ` Eli Zaretskii [this message]
2017-01-29 17:30 ` Eli Zaretskii
2017-01-29 17:47 ` Stefan Monnier
2017-01-29 20:16 ` Eli Zaretskii
2017-01-29 23:05 ` Paul Eggert
2017-01-30 15:33 ` Eli Zaretskii
2017-01-30 21:52 ` Paul Eggert
2017-01-31 15:48 ` Eli Zaretskii
2017-01-31 16:31 ` Stefan Monnier
2017-01-31 16:59 ` Paul Eggert
2017-02-02 0:01 ` Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ziid1tfi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.