From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: while-no-input interrupted by *shell*
Date: Mon, 24 Sep 2018 19:14:41 +0300 [thread overview]
Message-ID: <8336tyc1ou.fsf@gnu.org> (raw)
In-Reply-To: <87sh1y535s.fsf@web.de> (message from Michael Heerdegen on Mon, 24 Sep 2018 17:24:47 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Mon, 24 Sep 2018 17:24:47 +0200
>
> I found another annoyance with `while-no-input': If you have a *shell*
> buffer producing output - for example run something like ls -R in
> *shell* - then `while-no-input' is obviously interrupted by what's going
> on there. For example
>
> (while-no-input (sit-for 100))
>
> immediately terminates when evaluated while such a shell buffer exists.
>
> Is this expected, and is there a way to avoid this behavior?
Is it while-no-input that returns immediately, or is it sit-for?
next prev parent reply other threads:[~2018-09-24 16:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 15:24 while-no-input interrupted by *shell* Michael Heerdegen
2018-09-24 16:14 ` Eli Zaretskii [this message]
2018-09-24 16:40 ` Stefan Monnier
2018-09-24 17:00 ` Eli Zaretskii
2018-09-24 18:35 ` Stefan Monnier
2018-09-24 18:48 ` Eli Zaretskii
2018-09-24 17:39 ` Michael Heerdegen
2018-09-24 18:00 ` Eli Zaretskii
2018-09-24 19:09 ` Michael Heerdegen
2018-09-24 19:06 ` Stefan Monnier
2018-09-25 13:09 ` Eli Zaretskii
2018-09-25 13:39 ` Michael Heerdegen
2018-09-25 14:14 ` Eli Zaretskii
2018-09-29 7:13 ` Eli Zaretskii
2018-09-25 15:25 ` BUFFER_SWITCH_EVENT (was: while-no-input interrupted by *shell*) Stefan Monnier
2018-09-25 16:01 ` Eli Zaretskii
2018-09-25 16:14 ` BUFFER_SWITCH_EVENT Stefan Monnier
2018-09-25 16:28 ` BUFFER_SWITCH_EVENT Eli Zaretskii
2018-09-25 17:19 ` BUFFER_SWITCH_EVENT Stefan Monnier
2018-09-25 17:28 ` BUFFER_SWITCH_EVENT Eli Zaretskii
2018-09-25 18:14 ` BUFFER_SWITCH_EVENT Stefan Monnier
2018-09-25 18:32 ` BUFFER_SWITCH_EVENT Eli Zaretskii
2018-09-25 19:05 ` BUFFER_SWITCH_EVENT Eli Zaretskii
2018-09-25 21:50 ` BUFFER_SWITCH_EVENT Stefan Monnier
2018-09-26 5:42 ` BUFFER_SWITCH_EVENT Eli Zaretskii
2018-09-26 12:27 ` BUFFER_SWITCH_EVENT Stefan Monnier
2018-09-24 21:23 ` while-no-input interrupted by *shell* Andreas Schwab
2018-09-25 10:36 ` Michael Heerdegen
2018-09-24 16:19 ` Stefan Monnier
2018-09-25 17:47 ` while-no-input and pending input (was: while-no-input interrupted by *shell*) Michael Heerdegen
2018-09-25 17:53 ` Drew Adams
2018-09-26 12:50 ` while-no-input and pending input Michael Heerdegen
2018-09-26 14:18 ` while-no-input and pending input (was: while-no-input interrupted by *shell*) Eli Zaretskii
2018-09-26 17:57 ` while-no-input and pending input Michael Heerdegen
2018-09-26 19:06 ` Eli Zaretskii
2018-10-12 15:38 ` Michael Heerdegen
2018-10-12 15:44 ` Stefan Monnier
2019-02-17 23:44 ` Michael Heerdegen
2019-02-18 17:08 ` Eli Zaretskii
2019-02-18 19:08 ` Óscar Fuentes
2019-02-18 19:23 ` Eli Zaretskii
2019-02-18 22:32 ` Michael Heerdegen
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=8336tyc1ou.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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.