Re: Async commands in M-x compile

[Giorgos Keramidas]

On Wed, 30 Jun 2010 11:58:06 +0200, Antoine Levitt <address@hidden> wrote:
> Ken Raeburn <address@hidden> writes:
>
>> On Jun 29, 2010, at 18:43, Antoine Levitt wrote:
>>> Hello,
>>> 
>>> Can someone explain to me why compile doesn't support asynchroneous
>>> commands, and especially why it silently fails instead of displaying an
>>> error message? I don't understand the mechanism involved here.
>>
>> The program run -- the shell -- exits (after having started some other
>> program in background).  The compilation command has finished, and
>> exited with an exit status that indicates success.  So, you're done.
>> I could argue that it "succeeded", though apparently not at doing
>> whatever it is that you think it should do.
>
> Yes, I would completely agree with that, except it _doesn't_ start the
> program. Try running "xclock &"

It may be starting the program and killing it too fast, e.g. because the
parent shell reaps its child processes before it exits.  Can you try
running a "nohup sh foo.sh" script that spawns the echo redirection to
see if this is indeed the case?