From: Daniel Colascione <dancol@dancol.org>
To: Johan Andersson <johan.andersson@burtcorp.com>
Cc: 24849@debbugs.gnu.org
Subject: bug#24849: Is Emacs put in idle mode when window is not focused?
Date: Tue, 1 Nov 2016 13:37:36 -0700 [thread overview]
Message-ID: <26658800-320f-359a-6e35-a9deb06d5ed0@dancol.org> (raw)
In-Reply-To: <CAF4YyTp9ywu85eEfdLZ9CesMJa=_L6fFdb7mXvEjP9aQcR6qVw@mail.gmail.com>
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.
>
next prev parent reply other threads:[~2016-11-01 20:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 8:44 bug#24849: Is Emacs put in idle mode when window is not focused? Johan Andersson
2016-11-01 16:22 ` Eli Zaretskii
2016-11-01 19:48 ` Johan Andersson
2016-11-01 20:13 ` Eli Zaretskii
2016-11-01 20:18 ` Johan Andersson
2016-11-01 20:28 ` Daniel Colascione
2016-11-01 20:33 ` Johan Andersson
2016-11-01 20:37 ` Daniel Colascione [this message]
2016-11-01 20:41 ` Johan Andersson
2016-11-01 20:44 ` Daniel Colascione
2016-11-01 20:51 ` Johan Andersson
2016-11-01 23:25 ` Alan Third
2016-11-02 8:00 ` Johan Andersson
2016-11-01 20:45 ` Eli Zaretskii
2016-11-01 20:52 ` Johan Andersson
2016-11-02 2:18 ` Richard Stallman
2016-11-02 8:10 ` Johan Andersson
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26658800-320f-359a-6e35-a9deb06d5ed0@dancol.org \
--to=dancol@dancol.org \
--cc=24849@debbugs.gnu.org \
--cc=johan.andersson@burtcorp.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).