[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit
From: |
Michael Heerdegen |
Subject: |
bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit |
Date: |
Sun, 24 Feb 2019 08:16:51 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
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.
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/18
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/22
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/25
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/25
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/26
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/26
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Michael Heerdegen, 2019/02/26
- bug#34535: 27.0.50; emacs -nw: while-no-input + sit-for + <KEY> => Quit, Eli Zaretskii, 2019/02/26