From: Bean <bean123@126.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: status update for grub 2 developments?
Date: Tue, 26 Jun 2007 02:41:31 +0800 [thread overview]
Message-ID: <20070625184131.GA3383@ws3.vdp.com> (raw)
In-Reply-To: <4687E920.8080803@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
On Sun, Jul 01, 2007 at 07:49:20PM +0200, adrian15 wrote:
> Bean escribió:
> >>Well, if people want to work on scripting or networking they should
> >>talk to me. I have lots of code on my hd that is incomplete or just
> >>not cleaned up. It would be a waste of time if it were rewritten.
> >>And please poke me a lot to get me to work... ;)
> >
> >I'm interested in scripting. What could I do to help you ?
>
> As long as you may re-read Marco_g source code you can try to fix a
> bug
> that I have found I suppose in the parser.
>
> If you type any command with a \ character not being inside " "
> characters it gives an grub internal error.
>
> echo "\n" --> OK
> echo \n fff --> GRUB INTERNAL ERROR
It's fixed, please test.
echo "\n"
\n
echo \n fff
n fff
Note: you need to apply the patch grub2-parser-u2.diff first.
--
Bean
[-- Attachment #2: grub2-parser-u2-1.diff --]
[-- Type: text/plain, Size: 604 bytes --]
* normal/lexer.c (check_textstate): Add GRUB_PARSER_STATE_ESC.
Index: normal/lexer.c
===================================================================
RCS file: /sources/grub/grub2/normal/lexer.c,v
retrieving revision 1.6
diff -u -r1.6 lexer.c
--- normal/lexer.c 4 Jun 2006 15:56:55 -0000 1.6
+++ normal/lexer.c 25 Jun 2007 18:27:59 -0000
@@ -41,7 +41,8 @@
{
return (state == GRUB_PARSER_STATE_TEXT
|| state == GRUB_PARSER_STATE_QUOTE
- || state == GRUB_PARSER_STATE_DQUOTE);
+ || state == GRUB_PARSER_STATE_DQUOTE
+ || state == GRUB_PARSER_STATE_ESC);
}
struct grub_lexer_param *
next prev parent reply other threads:[~2007-06-25 18:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 12:47 status update for grub 2 developments? Vesa Jääskeläinen
2007-06-17 13:34 ` Robert Millan
2007-06-18 2:52 ` Ashok kumar
2007-06-18 10:22 ` adrian15
2007-06-18 13:32 ` Robert Millan
2007-06-18 15:40 ` Vesa Jääskeläinen
2007-06-19 12:13 ` adrian15
2007-06-19 15:13 ` Vesa Jääskeläinen
2007-06-19 12:08 ` adrian15
2007-06-23 12:57 ` Marco Gerards
2007-06-23 14:31 ` Bean
2007-06-23 14:50 ` Marco Gerards
2007-06-24 4:22 ` Bean
2007-06-24 11:47 ` Bean
2007-07-22 12:42 ` Marco Gerards
2007-06-23 14:52 ` Marco Gerards
2007-06-23 15:59 ` Bean
2007-06-23 16:10 ` Marco Gerards
2007-06-23 16:23 ` Bean
2007-06-23 16:38 ` Marco Gerards
2007-06-23 20:19 ` Yoshinori K. Okuji
2007-07-01 17:49 ` adrian15
2007-06-25 18:41 ` Bean [this message]
2007-06-26 4:13 ` Ashok kumar
2007-07-22 14:31 ` Marco Gerards
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=20070625184131.GA3383@ws3.vdp.com \
--to=bean123@126.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.