Re: Surprising behavior with inline environment variable expansion

2025-04-05 Thread Andreas Schwab
On Mär 31 2025, Chet Ramey wrote: > It's hard to see these as being useful if they're glibc-specific. They are coming from ISO TR 14652 and 30112. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely

Is this a bug?

2025-04-05 Thread George R Goffe
Howdy, This system is a Fedora 42 x86_64 system. I've been trying to build bash from a repository "https://git.savannah.gnu.org/git/bash.git"; and a having the devil's own time in the process. Did I just catch the repository in the middle of a rework? I have a full log of the build process if

Re: Surprising behavior with inline environment variable expansion

2025-04-05 Thread Andreas Schwab
On Mär 26 2025, Andreas Kähäri wrote: > The argument to "bash -c" There is no "bash -c" in that command. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."

Re: ;exit in bash history causes bash to exit

2025-04-05 Thread Ethan Gascoigne
I do have an alias with `&& exit` in it, but removing that alias doesn't get rid of the bug. I've tested it on another system (Xubuntu 24.04, stock install), and the issue didn't occur. Narrowed it down to the line `eval "$(fasd --init auto)"` in my .bashrc. Must be some kindof bug with fasd (http

2.0..devel: `set -u; a=1; echo ${#a[@]}' fails

2025-04-05 Thread Koichi Murase
With nounset, ${#a[@]} for a scalar variable fails even though we can correctly obtain the result (which is consistent with the expansion of "${a[@]}") without nounset. This is the result with the devel version: $ bash -c 'a=1; echo ${#a[@]}' 1 $ bash -uc 'a=1; echo ${#a[@]}' bash: line 1