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: Mon, 8 Oct 2018 21:39:53 +0100 Message-ID: References: <83sh1gzdey.fsf@gnu.org> <83in2cyymt.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000005cef5d0577bda0c0" X-Trace: blaine.gmane.org 1539031150 26593 195.159.176.226 (8 Oct 2018 20:39:10 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 8 Oct 2018 20:39:10 +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 Mon Oct 08 22:39:06 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 1g9cIv-0006gd-46 for geb-bug-gnu-emacs@m.gmane.org; Mon, 08 Oct 2018 22:39:01 +0200 Original-Received: from localhost ([::1]:48242 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9cL1-00031d-Kx for geb-bug-gnu-emacs@m.gmane.org; Mon, 08 Oct 2018 16:41:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46960) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g9cKv-00031U-FR for bug-gnu-emacs@gnu.org; Mon, 08 Oct 2018 16:41:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g9cKs-0003eX-8i for bug-gnu-emacs@gnu.org; Mon, 08 Oct 2018 16:41:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:36594) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g9cKs-0003eN-4q for bug-gnu-emacs@gnu.org; Mon, 08 Oct 2018 16:41:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g9cKs-0005uw-0h for bug-gnu-emacs@gnu.org; Mon, 08 Oct 2018 16:41: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: Mon, 08 Oct 2018 20:41:01 +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.153903121422672 (code B ref 32986); Mon, 08 Oct 2018 20:41:01 +0000 Original-Received: (at 32986) by debbugs.gnu.org; 8 Oct 2018 20:40:14 +0000 Original-Received: from localhost ([127.0.0.1]:40852 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g9cK5-0005tb-RG for submit@debbugs.gnu.org; Mon, 08 Oct 2018 16:40:14 -0400 Original-Received: from mail-qt1-f176.google.com ([209.85.160.176]:44892) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g9cK4-0005tL-5J for 32986@debbugs.gnu.org; Mon, 08 Oct 2018 16:40:12 -0400 Original-Received: by mail-qt1-f176.google.com with SMTP id c56-v6so22392388qtd.11 for <32986@debbugs.gnu.org>; Mon, 08 Oct 2018 13:40:12 -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=NvlPDyOThVtr8XOmXjOGRltJOQ7WX6fHnPwOZ9/lr2k=; b=c5EviOjhytBD4oLLsl8BWiM8iuv/92ftHDncdeGthdTijySSrM1E122d/fBPFvkc4T wni0w0yIu6DQKHlEbJpwINV+ZoBI5achy9mF5CN8n46EklitYUJ4jS+YIlRTIzs17RHm ftgD6WevasXxEDJE6A8hC5iXgfMPAtdMvzQjYF8Xn5UF/PgtZlH09Um6CU4gJ6sZf0Nv 2/LUvaFNPI3G61RgnE/Njlv39VTPzqIn+W2aXgmEAen7zP0mQULAzdhGNBYMLQCneu31 woKbI3KLIveJPq7pRxA0yQcESWozdlHbtu0b/MEchNxiDcDlhsk0YPmCZYLdW93uNSoq kZgA== 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=NvlPDyOThVtr8XOmXjOGRltJOQ7WX6fHnPwOZ9/lr2k=; b=BS54Z6LjD22z3vud4sX+VAJzYkcs6gG/+jRRwZele/aBGPJDv5ki03RmA75BuGfZ5+ snU2XOGs+krzmKkzqZpoV/sXjsdDhiEfpAV/THoi/9o/gqAPxFdxzajUQvb91SxFx7md 7e58TTstR35symCrkPQ57AqVxJWCURUs+JVL+EhvNlyK/Bsv/Sm4nQlfP1vvtMSr5UDz ewBDpm08Us5klb42d/C7Z8Je6tMccf/JNDL4ualQu+RChFq7OCJEzIwqmYxBZxpiI7Gs EAliClwDlW/g8vvS+cZ2BmIAZ6mQXqK4tQL08tdSY35MSLvELWc4NMlaZBcXd0911SR7 o6GQ== X-Gm-Message-State: ABuFfogqc11ZUGsjZscLW+O3MdxeTD4wao34/AhmzBnbLk6LxzMpHuk3 4r14iGyO6zKiSZwFJlH8RAnTY3mvIIUl+sTwBD8= X-Google-Smtp-Source: ACcGV62Dtx4rwc0wcecEt/+Hssu0vYF538gUSegr5IaJip4bZ8fQldoz2Q2NgOkldsAOH2w6YIBEW04aCDfTuAz0fg8= X-Received: by 2002:ac8:435b:: with SMTP id a27-v6mr20142040qtn.295.1539031206521; Mon, 08 Oct 2018 13:40:06 -0700 (PDT) In-Reply-To: <83in2cyymt.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:151025 Archived-At: --0000000000005cef5d0577bda0c0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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? If so, there's some unfortunate combination of factors that cause a hard-to-reproduce hang in Emacs, at least in the packages where I use it. But that's a matter for a future issue... Thanks, Jo=C3=A3o On Mon, Oct 8, 2018, 21:25 Eli Zaretskii wrote: > > From: Jo=C3=A3o T=C3=A1vora > > Date: Mon, 8 Oct 2018 21:06:12 +0100 > > Cc: 32986@debbugs.gnu.org > > > > I will fully read and process your thorough reply later tonight or > tomorrow, but in the meantime let me just > > restate, or clarify in case it wasn't clear, that I expect the 30s, 15s > and 0.1s case to break equally as quickly, > > namely as quick as I can type the first input. > > > > And indeed that's what happens on Linux and Mac OSX, but not on > Windows. If your reply already addresses > > this apparent discrepancy, then I apologize for my premature > clarification in advance. > > I didn't investigate the difference in behavior between Windows and > GNU/Linux, because I see similar behavior on both systems if I > neutralize all the "contaminating" factors which I described. It is > possible that it's easier to get the 30-sec delay on Windows because > keyboard input works without signals there, and uses messaging between > 2 threads running within the Emacs process. > > In any case, my point is that your expectation for immediate return is > incorrect, and I tried to explain why. > --0000000000005cef5d0577bda0c0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you for the clarification. I have now read the orig= inal explanation, 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 t= hat I can expect immediate return there?

If so, there's some unfortunate combination of factors that = cause a hard-to-reproduce hang in Emacs, at least in the packages where I u= se it.=C2=A0 But that's a matter for a future issue...

Thanks,
Jo=C3=A3o=

On Mon, Oct 8, = 2018, 21:25 Eli Zaretskii <eliz@gnu.org<= /a>> wrote:
> From: Jo=C3=A3o= T=C3=A1vora <joaotavora@gmail.com>
> Date: Mon, 8 Oct 2018 21:06:12 +0100
> Cc: 32986@debbugs.gnu.org
>
> I will fully read and process your thorough reply later tonight or tom= orrow, but in the meantime let me just
> restate, or clarify in case it wasn't clear, that I expect the 30s= , 15s and 0.1s case to break equally as quickly,
> namely as quick as I can type the first input.
>
> And indeed that's what happens on Linux and Mac OSX, but not on Wi= ndows.=C2=A0 If your reply already addresses
> this apparent discrepancy, then I apologize for my premature clarifica= tion in advance.

I didn't investigate the difference in behavior between Windows and
GNU/Linux, because I see similar behavior on both systems if I
neutralize all the "contaminating" factors which I described.=C2= =A0 It is
possible that it's easier to get the 30-sec delay on Windows because keyboard input works without signals there, and uses messaging between
2 threads running within the Emacs process.

In any case, my point is that your expectation for immediate return is
incorrect, and I tried to explain why.
--0000000000005cef5d0577bda0c0--