From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 1392ec7 2/3: A quicker check for quit
Date: Sun, 29 Jan 2017 12:47:57 -0500 [thread overview]
Message-ID: <jwvfuk1higo.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <83h94hydrs.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 29 Jan 2017 19:30:47 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
[...]
Thanks. This nicely matches what I remember, but I wasn't sure (I'm
obviously quite familiar with this story, since I was the one who
introduced the SYNC_INPUT changes, yet I never quite understood the
details of the immediate_quit thingy).
> This is why we started inserting QUIT in places that could potentially
> hang or take a long time -- to allow the user to interrupt them sooner
> rather than later. And that is why the recent changes which removed
> QUIT and added setting immediate_quit non-zero are a move in the wrong
> direction -- we should be doing the exact opposite.
So, IIUC we should basically get rid of immediate_quit.
Since I never really understood it, I'd be happy to see it disappear ;-)
[ But, it's obviously not urgent. ]
Stefan
next prev parent reply other threads:[~2017-01-29 17:47 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
2017-01-29 17:30 ` Eli Zaretskii
2017-01-29 17:47 ` Stefan Monnier [this message]
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=jwvfuk1higo.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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.