Thanks for your attention and the provided reduced patch. I can
confirm that, applied over bash-5.0.16, this solves my issue, both on
the test case as well as the bigger application from which it was
extracted.
Regards,
- Joan Bruguera
On Thu, 2 Apr 2020 at 23:20, Chet Ramey wrote:
>
> On 4/1/20
On 4/1/20 10:15 PM, Joan Bruguera Micó wrote:
> I'm having a problem with a script that used to work, which I reduced
> to the following test case:
>
> #!/bin/bash
>
> function docat() {
> for x in 1 2 3 ; do true; done
> cat "$@"
> }
>
> for x in $(seq 25); do
>
On 4/2/20 8:09 AM, Oğuz wrote:
> While reading commands from stdin, if job controls are enabled,
> commands following an asynchronous list in `{ cmd; } &` fashion are
> executed twice.
Thanks for the report. This will be fixed in the next devel branch push.
--
``The lyf so short, the craft so l
After the editor invoked by edit-and-execute-command exits, the
about-to-be-executed command (as edited by the editor) is echoed, but seemingly
as if [set -v] was set, causing a command executed before the edited command as
the result of a trap DEBUG to be echoed, as well. This is annoying for exam
While reading commands from stdin, if job controls are enabled,
commands following an asynchronous list in `{ cmd; } &` fashion are
executed twice. See below extract:
$ bash -m <<\EOD
{ sleep 1; } &
wait
echo $BASHPID
EOD
10615
10615
When job controls are disabled, or an external utility is calle
