From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, 34535@debbugs.gnu.org
Subject: bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit
Date: Sun, 24 Feb 2019 08:16:51 +0100 [thread overview]
Message-ID: <878sy5r6zg.fsf@web.de> (raw)
In-Reply-To: <834l8urk3j.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 23 Feb 2019 10:21:20 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Please note that using while-no-input with BODY that reads some input
> in a way causes indeterminate results, because whether the arriving
> input will be read and consumed by BODY and/or used to throw control
> flow out of BODY, depends on seemingly random factors, like whether
> Emacs checks quit-flag before or after BODY consumes the input and
> acts upon it.
I hope this is not the case in my code. In the w-n-i BODY I perform a
computation, but as in the skeleton I posted, the BODY itself doesn't
read input. The w-n-i with the computation is done in a function in
'minibuffer-setup-hook'. Is that allowed?
Thanks,
Michael.
next prev parent reply other threads:[~2019-02-24 7:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 22:29 bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit Michael Heerdegen
2019-02-22 16:08 ` Eli Zaretskii
2019-02-22 20:09 ` Eli Zaretskii
2019-02-22 20:25 ` Eli Zaretskii
2019-02-23 4:27 ` Michael Heerdegen
2019-02-23 8:21 ` Eli Zaretskii
2019-02-23 15:13 ` Stefan Monnier
2019-02-23 16:54 ` Eli Zaretskii
2019-02-24 7:16 ` Michael Heerdegen [this message]
2019-02-24 16:06 ` Eli Zaretskii
2019-02-25 7:09 ` Michael Heerdegen
2019-02-25 15:33 ` Eli Zaretskii
2019-02-26 9:56 ` Michael Heerdegen
2019-02-26 15:26 ` Eli Zaretskii
2019-02-26 17:27 ` Michael Heerdegen
2019-02-26 18:27 ` Eli Zaretskii
2019-03-01 10:21 ` Eli Zaretskii
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=878sy5r6zg.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=34535@debbugs.gnu.org \
--cc=eliz@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.