From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: bug-grub@gnu.org, Andreas Born <futur.andy@googlemail.com>
Subject: Re: [bug #27695] parser.sh ignores the closing quote when preceeded by a variable
Date: Fri, 16 Oct 2009 20:35:31 +0200 [thread overview]
Message-ID: <20091016183531.GD7037@thorin> (raw)
In-Reply-To: <4AD72362.3030805@gmail.com>
On Thu, Oct 15, 2009 at 03:28:02PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> diff --git a/script/sh/lexer.c b/script/sh/lexer.c
> index a30e3c0..0c71dae 100644
> --- a/script/sh/lexer.c
> +++ b/script/sh/lexer.c
> @@ -350,9 +350,11 @@ grub_script_yylex (union YYSTYPE *yylval, struct grub_parser_param *parsestate)
> if (! (check_varstate (newstate)))
> {
> if (state->state == GRUB_PARSER_STATE_VARNAME2
> - || state->state == GRUB_PARSER_STATE_QVARNAME2)
> - nextchar (state);
> - state->state = newstate;
> + || state->state == GRUB_PARSER_STATE_QVARNAME2)
> + {
> + nextchar (state);
> + state->state = newstate;
> + }
> break;
> }
>
> @@ -378,7 +380,6 @@ grub_script_yylex (union YYSTYPE *yylval, struct grub_parser_param *parsestate)
>
> buffer[bufpos++] = 0;
>
> - state->state = newstate;
> yylval->arg = grub_script_arg_add (parsestate, yylval->arg,
> GRUB_SCRIPT_ARG_TYPE_VAR, buffer);
> grub_dprintf ("scripting", "vartoken=`%s'\n", buffer);
Same here, I'm afraid.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-10-16 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091013-211116.sv74720.58002@savannah.gnu.org>
2009-10-15 13:28 ` [bug #27695] parser.sh ignores the closing quote when preceeded by a variable Vladimir 'phcoder' Serbinenko
2009-10-16 18:35 ` Robert Millan [this message]
2009-12-06 22:57 ` Andreas Born
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091016183531.GD7037@thorin \
--to=rmh@aybabtu.com \
--cc=bug-grub@gnu.org \
--cc=futur.andy@googlemail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox