Re: Meta: `help cut` doesn't document what -a does

On Fri, Jun 13, 2025 at 7:02 AM Duncan Roe wrote: > Fine for `make install' to *install* them. But it flies in the face of > convention for `make install' to *build* them - `make' should do that. `make' should only build bash; documentation, loadables, etc. should have dedicated targets. If build

Re: Meta: `help cut` doesn't document what -a does

On Wed, Jun 11, 2025 at 10:38:17AM -0400, Chet Ramey wrote: > The business of installing the loadables and > headers on `make install' came later as the result of feature requests. > Fine for `make install' to *install* them. But it flies in the face of convention for `make install' to *build* them

Re: exec3.sub never finishes with huge argmax

On 6/12/25 9:17 AM, Joel Ebel wrote: On Thu, Jun 12, 2025 at 9:09 AM Joel Ebel > wrote: On Wed, Jun 11, 2025 at 4:03 PM Chet Ramey mailto:chet.ra...@case.edu>> wrote: On 6/7/25 4:42 PM, Joel Ebel via Bug reports for the GNU Bourne Again SHell

Re: 5.3: Why is <(cmd) allowed in func names of func defs?

Date:Thu, 12 Jun 2025 12:26:17 -0400 From:Chet Ramey Message-ID: <86c23b56-de98-431d-be83-727013b65...@case.edu> | This isn't unreasonable, at least for the change to allow quoted characters | in function names. If that also includes any characters which would ne

Re: 5.3: Why is <(cmd) allowed in func names of func defs?

On 6/12/25 10:11 AM, Robert Elz wrote: It would be better to revert all the changes related to what's allowed in function names, than to go on allowing unquoted operator characters to be embedded in them (before quote removal), that's just broken. This isn't unreasonable, at least for the chan

Re: 5.3: Why is <(cmd) allowed in func names of func defs?

Date:Thu, 12 Jun 2025 09:09:42 -0400 From:Chet Ramey Message-ID: <3ed55e81-00e3-4f91-8fdd-f7fba7bc9...@case.edu> | >| That wouldn't have been backwards compatible, so I didn't add quote | >| removal. | > Really, in what cases? | In every case. If y

Re: exec3.sub never finishes with huge argmax

On Thu, Jun 12, 2025 at 9:09 AM Joel Ebel wrote: > > > On Wed, Jun 11, 2025 at 4:03 PM Chet Ramey wrote: > >> On 6/7/25 4:42 PM, Joel Ebel via Bug reports for the GNU Bourne Again >> SHell >> wrote: >> >> > I appreciate the effort to make the test run more efficiently and >> faster, >> > and tha

Re: 5.3: Why is <(cmd) allowed in func names of func defs?

On 6/11/25 7:51 PM, Robert Elz wrote: Date:Wed, 11 Jun 2025 10:09:46 -0400 From:Chet Ramey Message-ID: | That wouldn't have been backwards compatible, so I didn't add quote | removal. Really, in what cases? In every case. If you don't perform quote r

Re: exec3.sub never finishes with huge argmax

On Wed, Jun 11, 2025 at 4:03 PM Chet Ramey wrote: > On 6/7/25 4:42 PM, Joel Ebel via Bug reports for the GNU Bourne Again > SHell > wrote: > > > I appreciate the effort to make the test run more efficiently and faster, > > and that's probably a good idea, but I think there still needs to be a > w

Re: 5.3: Why is <(cmd) allowed in func names of func defs?

On 6/11/25 7:39 PM, Robert Elz wrote: Date:Wed, 11 Jun 2025 10:07:37 -0400 From:Chet Ramey Message-ID: <7ef0aaf1-e56e-433e-9d29-4ad232871...@case.edu> | That's the function name. In general, a function name is a WORD that | does not undergo any word expansi

Re: 5.3: Why is <(cmd) allowed in func names of func defs?

Date:Wed, 11 Jun 2025 10:09:46 -0400 From:Chet Ramey Message-ID: | That wouldn't have been backwards compatible, so I didn't add quote | removal. Really, in what cases? Like Koichi Murase showed, I can't find any way to get a quote char (without objection) int