On 18/06/2014 17:36 +0400, Henry S. Thompson wrote:
> Filipp Gunbin writes:
>
>> When I call such a script (catalina.sh, for example), its output is
>> displayed in *Asynchronous Shell Command*, but the program starting from
>> it with & (java usually) is not started (or started and killed
>> imme
Filipp Gunbin writes:
> When I call such a script (catalina.sh, for example), its output is
> displayed in *Asynchronous Shell Command*, but the program starting from
> it with & (java usually) is not started (or started and killed
> immediately). I supposed that maybe it's killed when the parent
On 18/06/2014 05:44 +0400, Ken Brown wrote:
> 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, s
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 al
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 alwa
5 matches
Mail list logo