On Tue, Oct 9, 2018, 03:32 Eli Zaretskii <
eliz@gnu.org> wrote:
> From: João Távora <joaotavora@gmail.com>
> Date: Mon, 8 Oct 2018 21:39:53 +0100
> Cc: 32986@debbugs.gnu.org
>
> Thank you for the clarification. I have now read the original explanation, and it makes sense. Ultimately, I think
> the sit-for is the right approach for my wait-for-any-process-or-input problem. Am I right to assume it's not
> affected by your explanation, and that I can expect immediate return there?
sit-for waits for keyboard input, so yes, it should return once the
user presses some key.
Right. A final question: process input is also considered during the sit-for, meaning a filter can throw to an enclosing tag and end it prematurely and immediately, right?