Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: kill % fails?
- X-seq: zsh-users 27379
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: dominik.vogt@xxxxxx, Zsh Users <zsh-users@xxxxxxx>
- Subject: Re: kill % fails?
- Date: Sat, 27 Nov 2021 18:15:32 -0800
- Archived-at: <https://zsh.org/users/27379>
- In-reply-to: <YaLcDXizEedUq5Pr@gmx.de>
- List-id: <zsh-users.zsh.org>
- References: <YaElhducf14tgEIU@gmx.de> <CAH+w=7YP-w4-9VDhTajLjXF8pot6xFuSLQzj4mKcV3pd0QfdMQ@mail.gmail.com> <YaLcDXizEedUq5Pr@gmx.de>
On Sat, Nov 27, 2021 at 5:32 PM Dominik Vogt <dominik.vogt@xxxxxx> wrote:
>
> I thought only the background processes woul be put in the job
> table?
No ... the "for" loop and each of the foreground commands also have
job table entries, to permit ^Z/bg/fg management. That's why you get
a full job table after 998 background jobs instead of 1000.
> Is there a way to print the command that could not be
> added?
Run with xtrace enabled?
For what it's worth, if you "setopt notify" (or rather, avoid "setopt
nonotify" which you must be getting from "sh" emulation?) you won't
fill the job table.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author