Re: 'wait -n' with and without id arguments

On 9/25/24 12:50 PM, Robert Elz wrote: Date:Wed, 25 Sep 2024 11:06:10 -0400 From:Chet Ramey Message-ID: | So you are saying that prompt notifications and `jobs' have the same | effect. POSIX implies but does not require this, and there is differing | be

Re: 'wait -n' with and without id arguments

Date:Wed, 25 Sep 2024 16:15:07 -0400 From:Chet Ramey Message-ID: <20daab70-09e2-4dfa-a98a-4ba29b622...@case.edu> | Do you think the text you quoted satisfies the "unless otherwise specified?" I think "unspecified whether it is removed at A or B" is fairly clear tha

Re: compgen -I (programmable completion as if initial word)

On 9/24/24 3:15 PM, Stephen Gildea wrote: I would like these two partially entered commands to complete the same way: $ ca $ sudo ca The first completion nicely takes into account any previous "complete -I" setting (because it is completing the initial word of a command). But the second comple

[sr #111125] compgen does not complete paths starting with environment variables when called indirectly

URL: Summary: compgen does not complete paths starting with environment variables when called indirectly Group: The GNU Bourne-Again SHell Submitter: None Submitted: Wed 25 Sep 2024 07:18

Re: 'wait -n' with and without id arguments

Date:Wed, 25 Sep 2024 11:06:10 -0400 From:Chet Ramey Message-ID: | So you are saying that prompt notifications and `jobs' have the same | effect. POSIX implies but does not require this, and there is differing | behavior among current implementatations. What i

Re: 'wait -n' with and without id arguments

On 9/8/24 8:35 PM, Zachary Santer wrote: This is still a discussion about interactive shell behavior only. What behavior do you want from the command lists that differs from what I described above? Since shell functions are essentially lists, you should get the same behavior from both. You'd