Greg Wooledge writes:
> On Tue, Jul 09, 2024 at 20:14:27 +, Erik Keever wrote:
>> A --debug-envvars flag which will, when passed to bash, catch every
>> time an environment variable is set and print the file/line that is
>> setting it. To restrict it, "--debug-envvars FOO,BAR" to catch only
>
On Tue, Jul 09, 2024 at 20:14:27 +, Erik Keever wrote:
> A --debug-envvars flag which will, when passed to bash, catch every time an
> environment variable is set and print the file/line that is setting it. To
> restrict it, "--debug-envvars FOO,BAR" to catch only instances of FOO or BAR
> b
Hello,
A recent conversation with a member of our research team leads me to propose
the following feature request:
A --debug-envvars flag which will, when passed to bash, catch every time an
environment variable is set and print the file/line that is setting it. To
restrict it, "--debug-envvar
On Tue, Jul 9, 2024 at 6:12 AM Zachary Santer wrote:
>
> command-1 | tee >( command-2 ) >( command-3 ) >( command-4 )
> wait
>
> The workaround for this not working would of course be named pipes,
> which is somewhat less trivial.
> Bash is already tracking the pids for all child processes not wa
On 7/7/24 6:55 AM, Koichi Murase wrote:
Bash Version: 5.3
Patch Level: 0
Release Status: alpha
Description:
The filtering by `shopt -u force_fignore' is also applied to the
suppression of completons unrelated to FIGNORE, which results in
strange behaviors in command- and directory-nam
On Fri, Jul 5, 2024 at 2:38 PM Chet Ramey wrote:
>
> On 6/29/24 10:51 PM, Zachary Santer wrote:
>
> so you were then able to wait for each process substitution individually,
> as long as you saved $! after they were created. `wait' without arguments
> would still wait for all process substitutions
