From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Johan Andersson Newsgroups: gmane.emacs.bugs Subject: bug#24849: Is Emacs put in idle mode when window is not focused? Date: Tue, 1 Nov 2016 21:41:48 +0100 Message-ID: References: <83oa1znpah.fsf@gnu.org> <83wpgnm014.fsf@gnu.org> <26658800-320f-359a-6e35-a9deb06d5ed0@dancol.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c06e6c4aa9bc00540435bdf X-Trace: blaine.gmane.org 1478033018 17121 195.159.176.226 (1 Nov 2016 20:43:38 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 1 Nov 2016 20:43:38 +0000 (UTC) Cc: 24849@debbugs.gnu.org To: Daniel Colascione Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Nov 01 21:43:33 2016 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 1c1ftp-0001Lk-HS for geb-bug-gnu-emacs@m.gmane.org; Tue, 01 Nov 2016 21:43:13 +0100 Original-Received: from localhost ([::1]:51146 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1ftr-0003I8-V5 for geb-bug-gnu-emacs@m.gmane.org; Tue, 01 Nov 2016 16:43:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49164) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1fth-0003GA-7u for bug-gnu-emacs@gnu.org; Tue, 01 Nov 2016 16:43:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c1fte-0000sh-4H for bug-gnu-emacs@gnu.org; Tue, 01 Nov 2016 16:43:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:52273) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c1fte-0000sa-1f for bug-gnu-emacs@gnu.org; Tue, 01 Nov 2016 16:43:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1c1ftd-0004xc-SI for bug-gnu-emacs@gnu.org; Tue, 01 Nov 2016 16:43:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Johan Andersson Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 01 Nov 2016 20:43:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 24849 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 24849-submit@debbugs.gnu.org id=B24849.147803294019014 (code B ref 24849); Tue, 01 Nov 2016 20:43:01 +0000 Original-Received: (at 24849) by debbugs.gnu.org; 1 Nov 2016 20:42:20 +0000 Original-Received: from localhost ([127.0.0.1]:39438 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1fsu-0004wY-HG for submit@debbugs.gnu.org; Tue, 01 Nov 2016 16:42:20 -0400 Original-Received: from mail-qk0-f169.google.com ([209.85.220.169]:34004) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1fsr-0004wL-Te for 24849@debbugs.gnu.org; Tue, 01 Nov 2016 16:42:14 -0400 Original-Received: by mail-qk0-f169.google.com with SMTP id q130so94644379qke.1 for <24849@debbugs.gnu.org>; Tue, 01 Nov 2016 13:42:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=burtcorp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PUua0fhax8TJjluwbSACxf+XW26kRxNmUvINUWzYzRw=; b=nkx6KMtcufCxVjcawTKdDNufdxqgnjTbAUy3uN7i5GiGvHtdFXvtLeFUsqAGVeRDlf cgS1ySxott3TvRbzVPWMA8ZMobWg2M0CGHcXsL35g2mFicCTd5pCSYKZudUJyj+rbsNI t1Bqg5b7dMDcgCDtcrL7z0Ucdm6VySbk6JE7hQyxKjdu0LIRmdE8NZQMcfjq0axI4XFU NV9tFAQIITH3mOn5gwMHY7K6JNitmSPUPqFvMmpq5E3VF6dKRG53vxLzPLqbTSETWqyj 9oYJ98gtfeWWMwLPgufEZ2T7vglQlaVr3UKPI5JOzmjnSkmyeCUm4LERlk8UTqk1/gZy CXOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PUua0fhax8TJjluwbSACxf+XW26kRxNmUvINUWzYzRw=; b=jJQ74a81XKR2UwYDvdg3eNLuYQysV5FJ8dN5CteoEqeWDhLQt1hP3FWVgbjbex/eiD 7sSM8z+1z2Fr5HEkpPmxzv4W2tqP5wSJCZtOT/S/Yk4zgZQEEX3dS/9sQO9c1cpDFtHf PlhWctejRv+WsyakDNmeVl85MttvzOR+0966NMSHHOMLZuqCQktWg5n3Z5fxSu7gL57/ zUiwPJyg/04WVy2IGAHhx8TChSZyOPGOkWtG5kNNlDVbhBMIuGS37aMGc76+9jRrQXnk bqmt3r24fqo+Wkk23ouRHdISwmI0gGxmncJ6221OdbMG4PntogBjv2E9pUpZIDRpQKv6 FFhQ== X-Gm-Message-State: ABUngvcabVYWsWmtlA+C/efXQP3xn/0mfy3JSKO92b4yCSd8PO/hcWxcm8wINzwmIcs6eZQkItIhG9sS+dOhog== X-Received: by 10.55.176.134 with SMTP id z128mr22695541qke.243.1478032928434; Tue, 01 Nov 2016 13:42:08 -0700 (PDT) Original-Received: by 10.237.38.33 with HTTP; Tue, 1 Nov 2016 13:41:48 -0700 (PDT) In-Reply-To: <26658800-320f-359a-6e35-a9deb06d5ed0@dancol.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:125241 Archived-At: --94eb2c06e6c4aa9bc00540435bdf Content-Type: text/plain; charset=UTF-8 On Tue, Nov 1, 2016 at 9:37 PM, Daniel Colascione wrote: > On 11/01/2016 01:33 PM, Johan Andersson wrote: > >> BTW: please don't top-post >>> >> >> Sorry, what? >> > > Please start your reply below the text to which you're replying. > > A: Because we read from top to bottom, left to right. > Q: Why should I start my reply below the quoted text? > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > > A: The lost context. > Q: What makes top-posted replies harder to read than bottom-posted? > > A: Yes. > Q: Should I trim down the quoted part of an email to which I'm > replying? > > > >> Are you sure that your subprocess isn't buffering its output? >>> >> >> No. Does that make a difference? >> > > Emacs can't respond to what it can't see. If your subprocess isn't pushing > bytes to the kernel and is instead buffering internally, Emacs can't see > those bytes. Internal buffering is a common cause of complaints about > parent processes not seeing output from children. > > >> Can you catch Emacs in the act? >>> >> >> What do you mean? >> >> Assuming GNU/Linux here. >>> >> >> On a Mac here, but I might be able to find a GNU/Linux machine at work >> tomo. >> > > dtrace, which OS X supports, has similar system-call-tracing capabilities, > although I don't know the correct incantation off the top of my head. > > >> > Please start your reply below the text to which you're replying. Ok, then I guess that's default in Gmail. This better? > ... Internal buffering is a common cause of complaints about parent processes not seeing output from children. I understand that, but that's not my issue here. The sub process might not have any output at all, but I would still expect that sub process to respond to my requests. -- Johan Andersson System Developer, Burt www.burtcorp.com Cell: +46 761 041607 https:// github.com/rejeep | http://twitter.com/rejeep | http://twitter.com/burtcorp --94eb2c06e6c4aa9bc00540435bdf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Tue, Nov 1, 2016 at 9:37 PM, Daniel Colascione <= ;dancol@dancol.org> wrote:
<= span class=3D"gmail-">On 11/01/2016 01:33 PM, Johan Andersson wrote:
BTW: please don't top-post

 Sorry, what?

Please start your reply below the text to which you're replying.

=C2=A0 =C2=A0 A: Because we read from top to bottom, left to right.
=C2=A0 =C2=A0 Q: Why should I start my reply below the quoted text?

=C2=A0 =C2=A0 A: Because it messes up the order in which people normally re= ad text.
=C2=A0 =C2=A0 Q: Why is top-posting such a bad thing?

=C2=A0 =C2=A0 A: The lost context.
=C2=A0 =C2=A0 Q: What makes top-posted replies harder to read than bottom-p= osted?

=C2=A0 =C2=A0 A: Yes.
=C2=A0 =C2=A0 Q: Should I trim down the quoted part of an email to which I&= #39;m replying?



Are you sure that your subprocess isn't buffering its output?

No. Does that make a difference?

 Emacs can't respond to what it can't see. If your subprocess isn= 9;t pushing bytes to the kernel and is instead buffering internally, Emacs = can't see those bytes. Internal buffering is a common cause of complain= ts about parent processes not seeing output from children.


Can you catch Emacs in the act?

What do you mean?

Assuming GNU/Linux here.

On a Mac here, but I might be able to find a GNU/Linux machine at work tomo= .

 dtrace, which OS X supports, has similar system-call-tracing capabilities, = although I don't know the correct incantation off the top of my head.


> Please start y= our reply below the text to which you're replying.

Ok, then I guess th= at's default in Gmail. This better?
=
> ... Internal buffering is a common cause of complaints = about parent processes not seeing output from children.

I understand that, but that's n= ot my issue here. The sub process might not have any output at all, but I w= ould still expect that sub process to respond to my requests.
--
--94eb2c06e6c4aa9bc00540435bdf--