On 3/1/17 3:32 PM, Reuti wrote:
>
> Am 01.03.2017 um 21:24 schrieb Grisha Levit:
>
>> On Wed, Mar 1, 2017 at 3:08 PM, Reuti <[email protected]> wrote:
>>> I would say not closed, as it's still happening in 4.4.12. And if it's
>>> closed, it should be reopened.
>>
>> Are you using the same example? I can reproduce Geoff's original test
>> case with 4.3 but not with 4.4..
>
> Ok, I can't reproduce the issue he found - correct this is gone. But the
> behavior I found:
>
> bash-4.4$ reset_vars
> bash-4.4$ assemble_fam2
> bash-4.4$ assemble_fam1
> bash-4.4$ say_families
> Flintstones=wilma:bam-bam:fred
> Rubbles=barney
>
> is still there.
This was fixed back in November as part of the work prompted by this
report:
http://lists.gnu.org/archive/html/bug-bash/2016-11/msg00101.html
I've attached a patch people can play around with.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU [email protected] http://cnswww.cns.cwru.edu/~chet/
*** ../bash-4.4-patched/parse.y 2016-09-11 11:31:46.000000000 -0400
--- parse.y 2017-03-01 16:04:15.574664915 -0500
***************
*** 4217,4220 ****
--- 4217,4221 ----
int orig_ind, nc, sflags, orig_eof_token;
char *ret, *s, *ep, *ostring;
+ STRING_SAVER *saved_pushed_strings;
/*yydebug = 1;*/
***************
*** 4229,4232 ****
--- 4230,4235 ----
save_input_line_state (&ls);
orig_eof_token = shell_eof_token;
+ saved_pushed_strings = pushed_string_list; /* separate parsing context */
+ pushed_string_list = (STRING_SAVER *)NULL;
/*(*/
***************
*** 4242,4245 ****
--- 4245,4250 ----
restore_input_line_state (&ls);
+ pushed_string_list = saved_pushed_strings;
+
token_to_read = 0;
