All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Born <futur.andy@googlemail.com>
To: GRUB2 Devel <grub-devel@gnu.org>
Subject: Re: [bug #27695] parser.sh ignores the closing quote when preceeded by	a variable
Date: Sun, 06 Dec 2009 23:57:51 +0100	[thread overview]
Message-ID: <4B1C36EF.1030203@googlemail.com> (raw)
In-Reply-To: <4AD72362.3030805@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2251 bytes --]

Problem exists still as of r1917. I've attached a rediffed version of 
Vladimir's patch.
The behaviour without the patch changed (it's even more confusing), but 
it's basically still the same:
grub> echo "$root"
grub>"
hd0,1

Vladimir 'phcoder' Serbinenko schrieb:
> Andreas Born wrote:
>   
>> URL:
>>   <http://savannah.gnu.org/bugs/?27695>
>>
>>                  Summary: parser.sh ignores the closing quote when preceeded
>> by a variable
>>   
>>     
> Attached patch should fix this bug
>   
>>                  Project: GNU GRUB
>>             Submitted by: shador
>>             Submitted on: Di 13 Okt 2009 21:11:16 GMT
>>                 Category: Terminal
>>                 Severity: Major
>>                 Priority: 5 - Normal
>>               Item Group: Software Error
>>                   Status: None
>>                  Privacy: Public
>>              Assigned to: None
>>          Originator Name: 
>>         Originator Email: 
>>              Open/Closed: Open
>>          Discussion Lock: Any
>>                  Release: 
>>                  Release: SVN
>>          Reproducibility: Every Time
>>          Planned Release: None
>>
>>     _______________________________________________________
>>
>> Details:
>>
>> The problem is reproducible with this example:
>>   
>>     
>>> set blub=blob
>>> echo $blub
>>>     
>>>       
>> blob
>>   
>>     
>>> echo "${blub}"
>>>     
>>>       
>> blob
>>   
>>     
>>> echo "$blub"
>>>
>>>     
>>>       
>> => fails, the closing quote is ignored
>>   
>>     
>>> echo "$blub""
>>>     
>>>       
>> blob
>> => works as workaround
>>
>> The real trouble starts with strings containing spaces. But it can be fixed,
>> as shown, by adding another quote at the end or using ${...}.
>>
>> This was tested with beta~4.
>>
>>
>>
>>
>>     _______________________________________________________
>>
>> Reply to this item at:
>>
>>   <http://savannah.gnu.org/bugs/?27695>
>>
>> _______________________________________________
>>   Nachricht geschickt von/durch Savannah
>>   http://savannah.gnu.org/
>>
>>
>>
>> _______________________________________________
>> Bug-grub mailing list
>> Bug-grub@gnu.org
>> http://lists.gnu.org/mailman/listinfo/bug-grub
>>
>>   
>>     
>
>
>   


[-- Attachment #2: varquote.diff --]
[-- Type: text/x-patch, Size: 757 bytes --]

=== modified file 'script/lexer.c'
--- script/lexer.c	2009-11-23 15:37:33 +0000
+++ script/lexer.c	2009-11-29 00:16:30 +0000
@@ -350,9 +350,11 @@
 	      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 @@
 
 	  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);

      parent reply	other threads:[~2009-12-06 22:58 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
2009-12-06 22:57   ` Andreas Born [this message]

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=4B1C36EF.1030203@googlemail.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.