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

Date:Wed, 21 Aug 2024 11:00:19 -0400 From:Chet Ramey Message-ID: <1b229634-888f-4f06-8761-c16d62501...@case.edu> | POSIX doesn't actually say that. It says, in a couple of different places, | "the message shall be written immediately prior to writing the next prom

Re: [PATCH] Correct error message when using -n and -o ignoreeof in interactive mode

Date:Wed, 21 Aug 2024 12:09:06 -0400 From:Grisha Levit Message-ID: | I've found using | | bash --norc -in <<< INPUT | | invaluable for testing input handling so I hope that remains an option. That kind of thing (not precisely that) is why the NetBSD s

Re: [PATCH] Correct error message when using -n and -o ignoreeof in interactive mode

On 8/21/24 12:09 PM, Grisha Levit wrote: On Wed, Aug 21, 2024, 11:27 Chet Ramey > wrote: On 8/19/24 9:52 AM, Ángel wrote: > On 2024-08-18 at 11:21 +0700, Robert Elz wrote: >> Interactive shells with -n (noexec) set are pointless > > The man pag

Re: [PATCH] Correct error message when using -n and -o ignoreeof in interactive mode

On Wed, Aug 21, 2024, 11:27 Chet Ramey wrote: > On 8/19/24 9:52 AM, Ángel wrote: > > On 2024-08-18 at 11:21 +0700, Robert Elz wrote: > >> Interactive shells with -n (noexec) set are pointless > > > > The man page states: > >>-n Read commands but do not execute them. This may

Re: please make the commit log clean

On 8/18/24 4:45 PM, shynur . wrote: Hi, Chet. I'm a beginner with Bash and recently stumbled upon the Bash code repository (specifically the 'devel' branch). I noticed that almost every commit includes thousands of lines of changes. Not really. Out of curiosity, I randomly clicked on one of

Re: [PATCH] Correct error message when using -n and -o ignoreeof in interactive mode

On 8/19/24 9:52 AM, Ángel wrote: On 2024-08-18 at 11:21 +0700, Robert Elz wrote: Interactive shells with -n (noexec) set are pointless The man page states: -n Read commands but do not execute them. This may be used to check a shell script for synta

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

On 8/21/24 9:25 AM, Chet Ramey wrote: On 8/14/24 4:42 PM, Robert Elz wrote: the implicit "jobs" before each PS1). POSIX doesn't actually say that. It says, in a couple of different places, "the message shall be written immediately prior to writing the next prompt for input," which implies th

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

On 8/21/24 9:27 AM, Chet Ramey wrote: On 8/15/24 2:39 AM, Zachary Santer wrote: I figured it out. I had to futz with Windows, MSYS, and then git to have the symlinks in the repo actually be real-deal symlinks. What are `real-deal' symlinks on Windows? The symlinks in the devel repo work fine

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

On 8/15/24 2:39 AM, Zachary Santer wrote: I figured it out. I had to futz with Windows, MSYS, and then git to have the symlinks in the repo actually be real-deal symlinks. What are `real-deal' symlinks on Windows? The symlinks in the devel repo work fine on Unix machines. -- ``The lyf so shor

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

On 8/14/24 4:42 PM, Robert Elz wrote: Date:Wed, 14 Aug 2024 15:21:44 -0400 From:Chet Ramey Message-ID: <1413a9a0-cbef-44c5-8072-a3be7294e...@case.edu> | I'm not sure returning the status of some random process from some | arbitrary point in the past is goin