Very often Bash 5.2 would suddenly stop saving command history which
has been confusing me for quite some time. Today I did some debugging
and came up with the following minimal scenario to reproduce the
problem.
$ bash --version
GNU bash, version 5.2.0(18)-beta (x86_64-apple-darwin21.5.0)
Copyri
On Tue, Jun 14, 2022 at 10:46:45PM -0700, AA via Bug reports for the GNU Bourne
Again SHell wrote:
> This
> is for a simple doc addition to the wait manpage,
Bash does not ship a man page named "wait". What are you actually
reading?
It's possible that your system is set up with the POSIX man pa
Date:Wed, 15 Jun 2022 07:37:07 -0400
From:Greg Wooledge
Message-ID:
| Bash does not ship a man page named "wait". What are you actually
| reading?
I assumed the section of "man bash" which describes the wait
builtin command, describes the various exit status po
On 6/15/22 3:00 AM, Clark Wang wrote:
> Very often Bash 5.2 would suddenly stop saving command history which
> has been confusing me for quite some time. Today I did some debugging
> and came up with the following minimal scenario to reproduce the
> problem.
Thanks for the report and the easy repr
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt
-DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/bin'
-DSTANDARD_UTILS_PATH='/usr/bin' -DSYS_BASHRC='/etc/bash
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt
-DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/bin'
-DSTANDARD_UTILS_PATH='/usr/bin' -DSYS_BASHRC='/etc/bash
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt
-DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/bin'
-DSTANDARD_UTILS_PATH='/usr/bin' -DSYS_BASHRC='/etc/bash
Greg: I included a link to the github. There are only 3 PRs, one of
which is mine. That's why I was suspicious it's the wrong place.
Here is a link to the actual patch:
https://github.com/gitGNU/gnu_bash/pull/5/files
Robert: Yes, I meant the section of "man bash" that discusses the
builtins
On Wed, Jun 15, 2022 at 12:14:22PM -0700, AA via Bug reports for the GNU Bourne
Again SHell wrote:
> Greg: I included a link to the github. There are only 3 PRs, one of which
> is mine. That's why I was suspicious it's the wrong place.
>
> Here is a link to the actual patch:
> https://github.com
On Wed, Jun 15, 2022 at 03:32:02PM -0400, Greg Wooledge wrote:
> On Wed, Jun 15, 2022 at 12:14:22PM -0700, AA via Bug reports for the GNU
> Bourne Again SHell wrote:
> > Greg: I included a link to the github. There are only 3 PRs, one of which
> > is mine. That's why I was suspicious it's the wro
On Jun 15 2022, Greg Wooledge wrote:
> That builtins.1 file clearly does not contain the ROFF source code for
> the content of builtins.0. Which makes me wonder where, exactly, the
> content of builtins.0 came from.
>From here:
.nr zZ 1
.so bash.1
> builtins.1 also contains this line, which I
Date:Wed, 15 Jun 2022 12:14:22 -0700
From:AA
Message-ID: <023de9fa-06b2-95f1-bf49-7d8a416a8...@memeplex.com>
| Therefore, if you
| could educate/direct me to the right place to ensure the patch at the
| link above is considered, I'd be happy to follow up.
I d
Paul Eggert wrote:
> It appears that PaSh itself isn't suitable for prime-time use.
That's my current conclusion too: I tried running PaSh on
- the configure script of a coreutils release,
- gnulib-tool (a large shell script),
and got a parse error in both cases [1].
Bruno
[1] https://github
13 matches
Mail list logo
