Re: 5.3-alpha: less readable output when set -x

> This is from https://lists.gnu.org/archive/html/bug-bash/2023-06/msg00092.htm > l > > It ensures e.g. that control characters are always displayed in a > printable manner. so that is definitely intentional and everything is now clear to me thanks a lot for your time ciao -gabriele

Bash Reference Manual: broken link

Hello GNU, 1. Perhaps there is a broken link in the bread crumb list of the index page of the Bash Reference Manual, found at: https://www.gnu.org/software/bash/manual/html_node/index.html The bread crumb list shows: Next: Introduction, Previous: (dir), Up: (dir) [Contents][Index] Each "(dir

[5.3-alpha] ">& /some/file" would fail when /some/file already exists

(I'm using the "devel" branch as the "bash-5.3-testing" branch failed to build for me. HEAD: 8c8daff1e3661c) To reproduce: $ bash53 --norc bash53-5.3# touch /tmp/file bash53-5.3# echo >& /tmp/file bash53: /tmp/file: File exists bash53-5.3#

Re: Bash-5.3-alpha available

On Tue, Apr 23, 2024 at 9:20 PM Chet Ramey wrote: > [..] > > and from the bash-5.3-testing branch in the bash git repository > (http://git.savannah.gnu.org/cgit/bash.git/log/?h=bash-5.3-testing). > You can use > > git clone --branch bash-5.3-testing git://git.savannah.gnu.org/bash.git > > to clone

Re: [5.3-alpha] ">& /some/file" would fail when /some/file already exists

On 4/25/24 12:18 PM, Clark Wang wrote: (I'm using the "devel" branch as the "bash-5.3-testing" branch failed to build for me. HEAD: 8c8daff1e3661c) To reproduce: $ bash53 --norc bash53-5.3# touch /tmp/file bash53-5.3# echo >& /tmp/file bash53: /tmp/file: File exists bash53-5.3# I can't reprod

Re: Bash-5.3-alpha available

On 4/25/24 12:31 PM, Clark Wang wrote: On Tue, Apr 23, 2024 at 9:20 PM Chet Ramey wrote: [..] and from the bash-5.3-testing branch in the bash git repository (http://git.savannah.gnu.org/cgit/bash.git/log/?h=bash-5.3-testing). You can use git clone --branch bash-5.3-testing git://git.savannah

Re: [5.3-alpha] ">& /some/file" would fail when /some/file already exists

On Thu, Apr 25, 2024, 14:55 Chet Ramey wrote: > On 4/25/24 12:18 PM, Clark Wang wrote: > > (I'm using the "devel" branch as the "bash-5.3-testing" branch failed > > to build for me. HEAD: 8c8daff1e3661c) > > > > To reproduce: > > > > $ bash53 --norc > > bash53-5.3# touch /tmp/file > > bash53-5.3#

Re: [5.3-alpha] ">& /some/file" would fail when /some/file already exists

On Thu, Apr 25, 2024 at 6:05 PM Grisha Levit wrote: > > On Thu, Apr 25, 2024, 14:55 Chet Ramey wrote: >> >> On 4/25/24 12:18 PM, Clark Wang wrote: >> > (I'm using the "devel" branch as the "bash-5.3-testing" branch failed >> > to build for me. HEAD: 8c8daff1e3661c) >> > >> > To reproduce: >> > >>

Re: bash parallel build: make[1]: warning: -j16 forced in submake: resetting jobserver mode.

On Mon, 22 Apr 2024 at 22:54, Chet Ramey wrote: > > On 4/22/24 11:58 AM, Chet Ramey wrote: > > On 4/20/24 2:02 AM, Cedric Blancher wrote: > > > >>> You can check what env the submake in question has and which recipe > >>> runs it and see where this setting comes from. > >> > >> We were only using

Re: [5.3-alpha] ">& /some/file" would fail when /some/file already exists

On Fri, Apr 26, 2024 at 2:53 AM Chet Ramey wrote: > > I can't reproduce it on macOS. > > $ ./bash --norc > $ touch some.file > $ echo >&some.file > $ rm some.file > $ touch /tmp/file > $ echo >& /tmp/file > $ rm /tmp/file > $ echo $BASH_VERSION > 5.3.0(1)-alpha I was using Debian (not sure about

Re: [5.3-alpha] ">& /some/file" would fail when /some/file already exists

On Fri, Apr 26, 2024 at 1:17 AM Grisha Levit wrote: > Actually, I see this on Ubuntu 22.04 but not on macOS. On Linux, O_EXCL and RX_EXPANDED (a flag used by bash to signal that the redirection word is already expanded) has the same value. I don't know why bash doesn't clear its internal flags bef