From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: while-no-input interrupted by *shell* Date: Mon, 24 Sep 2018 19:14:41 +0300 Message-ID: <8336tyc1ou.fsf@gnu.org> References: <87sh1y535s.fsf@web.de> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1537805654 23982 195.159.176.226 (24 Sep 2018 16:14:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 24 Sep 2018 16:14:14 +0000 (UTC) Cc: emacs-devel@gnu.org To: Michael Heerdegen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 24 18:14:10 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g4TUw-00067e-IP for ged-emacs-devel@m.gmane.org; Mon, 24 Sep 2018 18:14:10 +0200 Original-Received: from localhost ([::1]:45991 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g4TX3-00082s-50 for ged-emacs-devel@m.gmane.org; Mon, 24 Sep 2018 12:16:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60846) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g4TVb-0007be-C4 for emacs-devel@gnu.org; Mon, 24 Sep 2018 12:14:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g4TVY-0007zQ-8w for emacs-devel@gnu.org; Mon, 24 Sep 2018 12:14:51 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:37479) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g4TVY-0007zM-5I; Mon, 24 Sep 2018 12:14:48 -0400 Original-Received: from [176.228.60.248] (port=2108 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1g4TVX-0005Da-OY; Mon, 24 Sep 2018 12:14:48 -0400 In-reply-to: <87sh1y535s.fsf@web.de> (message from Michael Heerdegen on Mon, 24 Sep 2018 17:24:47 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:230021 Archived-At: > From: Michael Heerdegen > 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?