2023年2月12日(日) 10:15 Robert Elz :
Thank you for the detailed explanations. I totally agree with you on
all the points.
> Chet can decide if making bash handle more cases than it currently does is
> worth it or not for bash and its users.
Yes, Chet will decide.
--
Koichi
Date:Sun, 12 Feb 2023 01:14:12 +0900
From:Koichi Murase
Message-ID:
| `jobs' can be overwritten by a shell function. For example, when a
| user wants to modify the behavior of `jobs' for interactive uses, a
| typical solution is to override `jobs' with a
2023年2月12日(日) 0:42 Robert Elz :
> Why would you want to ever say "builtin jobs" though?
> The jobs command has to be buikt in to work.
`jobs' can be overwritten by a shell function. For example, when a
user wants to modify the behavior of `jobs' for interactive uses, a
typical solution is to
root@localhost:~# ( sleep .1 & jobs ) | wc -c
41
On Sat, Feb 11, 2023, 3:57 PM 岡部将幸 wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -g -O2
> uname output: Linux gold 5.8.0-63-generic #71-Ubuntu
2023年2月11日(土) 23:57 岡部将幸 :
> Description:
> builtin command "jobs" behaves differntly depending on
> the presence or absence of "builtin".
> "jobs" outputs to stdout, but "builtin jobs" does not
> output to stdout.
This seems to be reproduced in all the Bash versions from 1.14.7 to
devel. The
Date:Sat, 11 Feb 2023 22:54:47 +0900
From:=?UTF-8?B?5bKh6YOo5bCG5bm4?=
Message-ID:
| "jobs" outputs to stdout, but "builtin jobs" does not
| output to stdout.
Your test is flawed. Processes in a pipeline are in a
subshell environment. That environment has
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2
uname output: Linux gold 5.8.0-63-generic #71-Ubuntu SMP Tue Jul 13
15:59:12 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu
Bash
