From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: emacs 24.3.1: output from async-shell-command is not always displayed
Date: Wed, 18 Jun 2014 01:44:00 -0000 [thread overview]
Message-ID: <53A0EF03.8060001@cornell.edu> (raw)
In-Reply-To: <86zjhbpf9b.fsf@w2139spb.ru.yotateam.com>
On 6/17/2014 2:22 PM, Filipp Gunbin wrote:
> Here are the steps to reproduce.
>
> M-& echo "sleep 1; ps &" > /tmp/1.sh
>
> Then M-& /tmp/1.sh (few times).
>
> On my machine, sometimes it gives the output in the *Async Shell
> Command* buffer, sometimes not. Without "sleep 1" the output is
> displayed almost always.
>
> M-! /tmp/1.sh displays the output always.
I'm seeing something different, but I'm running a pretest of emacs-24.4
rather than emacs-24.3. I find that the output is never displayed, with
or without "sleep 1". But if I remove the "&" from 1.sh, then the
output is always displayed (again, with or without "sleep 1"). Could
you try installing the test release emacs-24.3.90-1 and see if you get
the same results I'm getting?
I don't know if there's a bug here or not. If there is, it's not
specific to Cygwin; I get the same behavior on Fedora 20.
Do you have a use case for wanting to call asynchronously a command
that's already running asynchronously (because of the "&")?
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-06-18 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 18:22 Filipp Gunbin
2014-06-17 18:27 ` Filipp Gunbin
2014-06-18 1:44 ` Ken Brown [this message]
2014-06-18 11:10 ` Filipp Gunbin
2014-06-18 13:37 ` Henry S. Thompson
2014-06-18 15:23 ` Filipp Gunbin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53A0EF03.8060001@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.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.
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).