[PATCH] rltech.texi: missing @end deftypevar

2024-02-12 Thread Grisha Levit
Building readline.info fails in the devel branch: $ make readline.info rltech.texi:2399: @node seen before @end deftypevar make: *** [readline.info] Error 1 --- lib/readline/doc/rltech.texi | 1 + 1 file changed, 1 insertion(+) diff --git a/lib/readline/doc/rltech.texi b/lib/readlin

[PATCH] expand_declaration_argument: handle mixed on/off opts

2024-02-12 Thread Grisha Levit
When assigning a variable as part of expanding a compound assignment argument, any [aAgGiIluc] options are treated as either all being on or all being off: $ unset X; declare -a +i X=(2+2); declare -p X declare -a X=([0]="4") $ unset X; declare +i -u X=(foo); declare -p X declare

Re: declare -A +A

2024-02-12 Thread Kerin Millar
On Tue, 13 Feb 2024 00:07:47 +0100 alex xmb sw ratchev wrote: > On Mon, Feb 12, 2024, 23:25 Koichi Murase wrote: > > > 2024年2月13日(火) 6:13 Chet Ramey : > > > Only for indexed and associative arrays, since those are the attributes > > > that cause changes in the underlying value storage format. T

Re: declare -A +A

2024-02-12 Thread Grisha Levit
On Mon, Feb 12, 2024 at 4:13 PM Chet Ramey wrote: > > On 2/7/24 2:23 AM, Grisha Levit wrote: > > If a single declare command both sets and unsets the array or assoc > > attribute for an existing scalar variable, the `value' member of the > > SHELL_VAR is assigned an ARRAY* or HASH_TABLE* as approp

Re: declare -A +A

2024-02-12 Thread alex xmb sw ratchev
On Mon, Feb 12, 2024, 23:25 Koichi Murase wrote: > 2024年2月13日(火) 6:13 Chet Ramey : > > Only for indexed and associative arrays, since those are the attributes > > that cause changes in the underlying value storage format. That's > different > > than turning the integer attribute on and off, for i

Re: declare -A +A

2024-02-12 Thread Koichi Murase
2024年2月13日(火) 6:13 Chet Ramey : > Only for indexed and associative arrays, since those are the attributes > that cause changes in the underlying value storage format. That's different > than turning the integer attribute on and off, for instance. > > Should it be an actual error, or should the shel

Re: Rendering the Bash man page with commercial Unix/System V nroff

2024-02-12 Thread G. Branden Robinson
[self-follow-up] At 2024-02-12T13:00:43-0600, G. Branden Robinson wrote: > I'm also attaching a sample document that people can use to test the > nroff(1)/man(7) on their system. If I had a nickel for every time I forget the attachment... > Here's how I tested it with groff, mandoc(1), Heirloom

Re: Rendering the Bash man page with commercial Unix/System V nroff

2024-02-12 Thread G. Branden Robinson
Hi Chet, At 2024-02-12T14:45:30-0500, Chet Ramey wrote: > On 2/12/24 2:00 PM, G. Branden Robinson wrote: > > I see that most of my proposed man page changes from the recent > > series landed in the devel branch. Thanks! > > > > I did notice that this one and its follow-up did not. Was that on >

Re: declare -A +A

2024-02-12 Thread Chet Ramey
On 2/7/24 2:23 AM, Grisha Levit wrote: If a single declare command both sets and unsets the array or assoc attribute for an existing scalar variable, the `value' member of the SHELL_VAR is assigned an ARRAY* or HASH_TABLE* as appropriate, but later ends up treated as a char*: $ bash-asan -c

Re: Rendering the Bash man page with commercial Unix/System V nroff

2024-02-12 Thread Chet Ramey
On 2/12/24 2:00 PM, G. Branden Robinson wrote: Hi Chet, I see that most of my proposed man page changes from the recent series landed in the devel branch. Thanks! I did notice that this one and its follow-up did not. Was that on purpose? Is there something I can do to improve the patch? I

Rendering the Bash man page with commercial Unix/System V nroff (was: [PATCH 17/18] doc/bash.1: migrate to strings for troublesome characters)

2024-02-12 Thread G. Branden Robinson
Hi Chet, I see that most of my proposed man page changes from the recent series landed in the devel branch. Thanks! I did notice that this one and its follow-up did not. Was that on purpose? Is there something I can do to improve the patch? The reason I submitted 17/18 and 18/18 is because, o

Re: internal error

2024-02-12 Thread Chet Ramey
On 2/12/24 12:02 PM, Frank Heckenbach wrote: On 2/10/24 9:41 PM, Frank Heckenbach wrote: % ./bash -c "set -e; f() { eval false; }; f" ./bash: line 1: pop_var_context: head of shell_variables not a function context Might be related to https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00073.

Re: internal error

2024-02-12 Thread Frank Heckenbach
> On 2/10/24 9:41 PM, Frank Heckenbach wrote: > > % ./bash -c "set -e; f() { eval false; }; f" > > ./bash: line 1: pop_var_context: head of shell_variables not a function > > context > > > > Might be related to > > https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00073.html, > > but still p

Re: Large command in bash history breaks rendering

2024-02-12 Thread Chet Ramey
On 2/10/24 8:16 AM, Flightkick wrote: Bash Version: 5.2 Patch Level: 26 Release Status: release Description:         Let me preface this bug report by stating that I am not entirely sure as to whether this issue is caused by bash, or by another component related to the bash ecosystem. I hope

Re: internal error

2024-02-12 Thread Chet Ramey
On 2/10/24 9:41 PM, Frank Heckenbach wrote: % ./bash -c "set -e; f() { eval false; }; f" ./bash: line 1: pop_var_context: head of shell_variables not a function context Might be related to https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00073.html, but still present in 5.2.21. Thanks, i