Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Synchronous vs. Asynchronous
- X-seq: zsh-users 15308
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxx
- Subject: Re: Synchronous vs. Asynchronous
- Date: Fri, 20 Aug 2010 10:36:38 -0700
- In-reply-to: <20100820164507.419dc0bc@xxxxxxx>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <100820083501.ZM29362@xxxxxxxxxxxxxxxxxxxxxx> <20100820164507.419dc0bc@xxxxxxx>
On Aug 20, 4:45pm, Peter Stephenson wrote:
}
} > So if we're going to cause zsh to wait for >(...), we should change
} > the description in the documentation to no longer say "asynchronous".
}
} Actually, I think it already does that, except in the case of a builtin not
} run inside { ... }
Based on Vincent's description, it's an external command not run inside
{ ... } for which it becomes asynchronous. Any builtin, including any
command in { ... }, does make it synchronous.
(All of this begs the question of what happens with <(...), but that's
less likely to be noticed by anyone.)
} My big remaining worry is whether the >(...) could think it's in the
} foreground when it's actually in the background after the patch in the
} second subthread.
Yes, mine too.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author