On 11/22/22 5:04 PM, Dabrien 'Dabe' Murphy wrote:
On 11/22/22 5:01 PM, Chet Ramey wrote:
Thanks for the report. It's an easy fix; bash was optimizing away the fork
and therefore not printing the timing information.
Awesome!
Hitting it with a hammer: $10
Knowing WHERE to hit it: $9
On 11/21/22 9:36 PM, Dabrien 'Dabe' Murphy wrote:
More crumbs, FTR:
19:51 this comment looks very suspicious
https://git.savannah.gnu.org/cgit/bash.git/diff/execute_cmd.c?h=devel&id=9928dcb48f35d957d936f9c6d8bec8cec8b76317
19:52 that patch addresses this bug
https://lists.gnu.org/arch
On 11/22/22 5:01 PM, Chet Ramey wrote:
Thanks for the report. It's an easy fix; bash was optimizing away the
fork
and therefore not printing the timing information.
Awesome!
Hitting it with a hammer: $10
Knowing WHERE to hit it: $9,990
«grin»
--
:- Dabe
On 11/21/22 7:07 PM, d...@dabe.com wrote:
Bash Version: 5.2
Patch Level: 9
Release Status: release
Description:
Under 5.2.x, measuring the `time` of a subshell -- `time ( sleep 1 )`
for example -- doesn't display any timing information,
whereas `5.1.x` and before did.
Thanks
On 11/22/22 2:43 AM, Lawrence Velázquez wrote:
The "Parameter Expansion" section of bash(1) simply does not use
boldface for "${" / "}". I don't know if that is intentional, but
I would guess that only the unique portions of each expansion form
are emphasized with boldface.
This is correct.
On 11/20/22 7:50 AM, Koichi Murase wrote:
This difference is caused because the slash after the backslash is
only checked after a matching character is found
(lib/glob/sm_loop.c:703). The same check should be applied also
before a matching character is found (lib/glob/sm_loop.c:573)
