Surprising results when profiling Bash

2024-08-24 Thread Martin D Kealey
I've been making some tentative patches to the `devel` branch, and since I have a fairly large bashrc, when I compile Bash with maximal debugging support, its startup is ... underwhelmingly slothful. So I decided to build it with profiling enabled, and see if I'd done something to ruin its perform

Re: Question on $@ vs $@$@

2024-08-24 Thread Steffen Nurpmeso
Steffen Nurpmeso wrote in <20240825013311.B3Z3QcNn@steffen%sdaoden.eu>: |Robert Elz wrote in | <26326.1724474...@jacaranda.noi.kre.to>: ||Date:Fri, 23 Aug 2024 23:47:06 +0200 ||From:Steffen Nurpmeso ||Message-ID: <20240823214706.oskn9OEF@steffen%sdaoden.eu> ||

Re: Question on differences on quoted $* (Was: Re: Question on $@ vs $@$@)

2024-08-24 Thread Steffen Nurpmeso
Emanuele Torre wrote in : |On Sat, Aug 24, 2024 at 02:15:48AM +0200, Steffen Nurpmeso wrote: |> Sorry but i really have to come again, i do not understand what is |> going on, and *i* think shell is at fault. | |No. It is working correctly. | |> This: |> |> a() { |> echo $#,1=$1,2

Re: Question on differences on quoted $* (Was: Re: Question on $@ vs $@$@)

2024-08-24 Thread Steffen Nurpmeso
Greg Wooledge wrote in : |On Sat, Aug 24, 2024 at 02:15:48 +0200, Steffen Nurpmeso wrote: |> a() { |> echo $#,1=$1,2=$2,"$*",$*, |>} | |You didn't read a word I said, did you I recognize that i did not get your email even though i was in Cc:. |*Sigh.* --End of --steffen | |De

Re: Question on $@ vs $@$@

2024-08-24 Thread Steffen Nurpmeso
Robert Elz wrote in <26326.1724474...@jacaranda.noi.kre.to>: |Date:Fri, 23 Aug 2024 23:47:06 +0200 |From:Steffen Nurpmeso |Message-ID: <20240823214706.oskn9OEF@steffen%sdaoden.eu> | || So IFS whitespace only if part of $IFS. | |That is the definition of IFS whi

Re: Question on $@ vs $@$@

2024-08-24 Thread Lawrence Velázquez
On Sat, Aug 24, 2024, at 10:08 PM, Steffen Nurpmeso wrote: > One hopefully last thing in this regard for me, > > c() { echo "$# 1<$1> 2<$2> 3<$3> *<$*> @<$@>"; } This easily obfuscates the structure of the "$@" expansion. You'd be better off with something like this, which prints each positiona

bash-5.2.32 fails "make install" on RHEL 9

2024-08-24 Thread Dennis Clarke via Bug reports for the GNU Bourne Again SHell
This seemed to happen over and over and only during "make install". So I went for a simple config just to get something. Config was trivial : $ ../bash-5.2.32/configure --prefix=/opt/bw \ --enable-minimal-config --enable-history --enable-job-control \ --enable-multibyte --enable-readline \ --

Re: Question on $@ vs $@$@

2024-08-24 Thread Lawrence Velázquez
On Sat, Aug 24, 2024, at 11:49 PM, Lawrence Velázquez wrote: > Correct. Since you're using $* unquoted in a context where field > splitting is performed, the shell does not expand it to a single > field. That is, unless there's a single positional parameter that is not further split. -- vq