From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#32986: 27.0.50; unexpected delay in while-no-input + accept-process-output Date: Tue, 9 Oct 2018 09:47:58 +0100 Message-ID: References: <83sh1gzdey.fsf@gnu.org> <83in2cyymt.fsf@gnu.org> <83h8hvzw70.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000001e3b670577c7cc5a" X-Trace: blaine.gmane.org 1539074829 9171 195.159.176.226 (9 Oct 2018 08:47:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 9 Oct 2018 08:47:09 +0000 (UTC) Cc: 32986@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Oct 09 10:47:05 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1g9nfV-0002Gx-Av for geb-bug-gnu-emacs@m.gmane.org; Tue, 09 Oct 2018 10:47:05 +0200 Original-Received: from localhost ([::1]:50250 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9nhb-0006Pp-LN for geb-bug-gnu-emacs@m.gmane.org; Tue, 09 Oct 2018 04:49:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39553) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9nhS-0006Pk-T0 for bug-gnu-emacs@gnu.org; Tue, 09 Oct 2018 04:49:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g9nhO-0002Ss-RK for bug-gnu-emacs@gnu.org; Tue, 09 Oct 2018 04:49:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:36902) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g9nhO-0002Sk-NE for bug-gnu-emacs@gnu.org; Tue, 09 Oct 2018 04:49:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g9nhO-0002SQ-Jj for bug-gnu-emacs@gnu.org; Tue, 09 Oct 2018 04:49:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 09 Oct 2018 08:49:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32986 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 32986-submit@debbugs.gnu.org id=B32986.15390748979357 (code B ref 32986); Tue, 09 Oct 2018 08:49:02 +0000 Original-Received: (at 32986) by debbugs.gnu.org; 9 Oct 2018 08:48:17 +0000 Original-Received: from localhost ([127.0.0.1]:41160 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g9nge-0002Qq-Le for submit@debbugs.gnu.org; Tue, 09 Oct 2018 04:48:16 -0400 Original-Received: from mail-qt1-f182.google.com ([209.85.160.182]:42507) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g9ngd-0002QY-Pl for 32986@debbugs.gnu.org; Tue, 09 Oct 2018 04:48:16 -0400 Original-Received: by mail-qt1-f182.google.com with SMTP id j46-v6so711146qtc.9 for <32986@debbugs.gnu.org>; Tue, 09 Oct 2018 01:48:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=N7ObH2x5zqy0fFK3jJWjWY1FFKzAo9ENIMIJraRSb8E=; b=VifvPq9dzRNOJnvxhZXHKizXIgEG3H78fdikneDaUQBoFcDZx5u6Qf0ldLFJIbJ4pr VWq0ET6+/6YwVz+fyFPiIiB2SCdwsd4msj+tY5B0sS32a1NQ9rLMCMbSzIn2tULQXBXP lLYfKT0R/WHgOJG7ldaKsN1AFz6Fb1L71mQvLMDf6ujmG5nDRd9YTNqgxJzBvIgcs6hn 5zYekpvWn0+ZTvCgbTDDhRykERTDme3+zvPk7HPf2urvffaz0VsOVv89X02cuLeRRtlL wjvznJZyHfsbF4ns06h3N9/yyCDhXXJqpQfvEQKX6k4bxp1+f/o2ItchREJsgDut0Qy3 BUFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=N7ObH2x5zqy0fFK3jJWjWY1FFKzAo9ENIMIJraRSb8E=; b=AgV3LvMIgoR+wL0zcEsiY7e78jAenViVUjzFMniSFviCnZXXbBm+HhX42zThled6x0 eOnnMGRMaGXus93Uel1odnPUiv8UkSX9z3ChzjESmPn035h5l6N4BUCZSa1xEHKClWxF Cxnu2Nckx2jdKZXNy3MMCd94YPRO5A5vAftKsTZqzEY+HPuIwu1Pk1LvOyoIq0Pl4Q/b IpEB6C23wZZ2PSgmLPkcpkbIK3oTNgPrN2SResOUjZ5G3YINEACB4IYGv29g5+L6/7hh ZON21Z7kaQ19uSR4yPH43jvzgYp1rO+Q/Qe/PWOEaV2l9hcQMTT3rOTnU4S817rK649m 0xNw== X-Gm-Message-State: ABuFfohf490YqnPOkBAQCo4ptcTRixg2P6kvMrAk/8iljXYC59JguCsr Qs29mBetGa++CN543nAnTu/EOq0wUGxlISDYfeDLQw== X-Google-Smtp-Source: ACcGV63jZIc5jwD0QazAm4xXLj9tyQBHti5F705TSbfbHk2MYHP+olUScsGeP2gYEsLiRswtIrzhZwJw8x8/WEd4tC4= X-Received: by 2002:aed:2647:: with SMTP id z65-v6mr21377452qtc.301.1539074890282; Tue, 09 Oct 2018 01:48:10 -0700 (PDT) In-Reply-To: <83h8hvzw70.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:151041 Archived-At: --0000000000001e3b670577c7cc5a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Oct 9, 2018, 03:32 Eli Zaretskii wrote: > > From: Jo=C3=A3o T=C3=A1vora > > 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? > --0000000000001e3b670577c7cc5a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


= On Tue, Oct 9, 2018, 03:32 Eli Zaretskii <eliz@gnu.org> wrote:
> = From: Jo=C3=A3o T=C3=A1vora <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 explanat= ion, and it makes sense.=C2=A0 Ultimately, I think
> the sit-for is the right approach for my wait-for-any-process-or-input= problem.=C2=A0 Am I right to assume=C2=A0 it's not
> affected by your explanation, and that I can expect immediate return t= here?

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 consid= ered during the sit-for, meaning a filter can throw to an enclosing tag and= end it prematurely and immediately, right?
--0000000000001e3b670577c7cc5a--