Re: wrong variable name in error message about unbound variable?

2023-10-16 Thread Grisha Levit
On Mon, Oct 16, 2023, 22:46 Christoph Anton Mitterer wrote: > Hey. > > On Mon, 2023-10-16 at 22:05 -0400, Lawrence Velázquez wrote: > > Under no circumstances should your examples complain about "array" > > because they do not attempt to expand it. As I demonstrated, your > > examples do not eve

Re: wrong variable name in error message about unbound variable?

2023-10-16 Thread Christoph Anton Mitterer
Hey. On Mon, 2023-10-16 at 22:05 -0400, Lawrence Velázquez wrote: > Under no circumstances should your examples complain about "array" > because they do not attempt to expand it.  As I demonstrated, your > examples do not even complain about unset scalar variables. Okay I realise now, why it work

Re: wrong variable name in error message about unbound variable?

2023-10-16 Thread Lawrence Velázquez
On Mon, Oct 16, 2023, at 9:06 PM, Christoph Anton Mitterer wrote: > $ set -u > $ [ -n "${array[key]+is_set}" ] && echo is set || echo not set > bash: key: unbound variable > $ [[ -v array[key] ]] && echo is set || echo not set > bash: key: unbound variable Since "array" has not been declared at th

wrong variable name in error message about unbound variable?

2023-10-16 Thread Christoph Anton Mitterer
Hey. On 5.2.15 I've noticed the following: $ set -u $ [ -n "${array[key]+is_set}" ] && echo is set || echo not set bash: key: unbound variable $ [[ -v array[key] ]] && echo is set || echo not set bash: key: unbound variable $ declare -A array $ [ -n "${array[key]+is_set}" ] && echo is set || ech

Re: [PATCH] repair recent, ill-conceived man page changes

2023-10-16 Thread Bjarni Ingi Gislason
On Wed, Oct 11, 2023 at 04:08:55AM -0500, G. Branden Robinson wrote: > Hi Chet, > > Please consider reverting the following recent changes to the bash man > page. Bjarni should have run them by the groff list first, because some > of them are ill-considered. > > Bjarni, > > I regret that I must

Re: e-mail address for reports concerning the bash manual

2023-10-16 Thread Chet Ramey
On 10/13/23 9:59 AM, Vincent Lefevre wrote: Hi, For reports concerning the bash manual, the tarballs (5.2, 5.2.15) and the Git repository say to Chet Ramey's address (both in the man page and in the HTML file). But https://www.gnu.org/software/bash/manual/html_node/Reporting-Bugs.html says

Re: variable set in exec'ing shell cannot be unset by child shell

2023-10-16 Thread Chet Ramey
On 10/14/23 12:03 PM, Robert Elz wrote: However in the case of a special built-in utility (which "." is) then the requirements are much stricter: � If the command name is a special built-in utility, variable assignments shall affect the current execution environment before the utility i

Re: variable set in exec'ing shell cannot be unset by child shell

2023-10-16 Thread Chet Ramey
On 10/15/23 12:31 AM, Martin D Kealey wrote: On Sun, 15 Oct 2023, 03:15 Ti Strga, wrote: I think I would attack this from an entirely different angle: what about simply modifying Baeh so that it slurps in the entire file upon opening it? Bash reads up to 8K at a time, minus bookkeeping over

Re: variable set in exec'ing shell cannot be unset by child shell

2023-10-16 Thread Chet Ramey
On 10/15/23 12:24 AM, Martin D Kealey wrote: On Sun, 15 Oct 2023, 03:05 Greg Wooledge, wrote: On Sat, Oct 14, 2023 at 12:55:21PM -0400, Ti Strga wrote: it's just the "[[ -v foo ]]" tests to see where along the cloning process we are. *Shudder* Likewise, b. If the *real* goal is to o

Re: variable set in exec'ing shell cannot be unset by child shell

2023-10-16 Thread Chet Ramey
On 10/14/23 12:46 AM, Martin D Kealey wrote: Respectfully I must disagree. This aspect of Bash's behaviour has a very long historical precedent. Back when I used the Bourne Shell we didn't have `local`, so we used to write `var= func` to make sure that `func` couldn't mess with *our* `var`.