All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Split of normal mode (version 2)
Date: Fri, 10 Apr 2009 08:49:57 +0900	[thread overview]
Message-ID: <200904100849.57251.okuji@enbug.org> (raw)
In-Reply-To: <ca0f59980904060939w4c46bb5ax6966a0c098016780@mail.gmail.com>

On Tuesday 07 April 2009 01:39:23 Bean wrote:
> Hi,
>
> This is another update of the patch.
>
> 1, Now completion.c is in menu.mod, and menu_viewer.c is in misc.mod,
> the reason for the switch is to allow configfile to depend on misc.mod
> only.

I think the name "misc.mod" is ugly. Can you think about a better name?

> 2, Auto generate handler.lst file, which contain module information
> for handlers. normal.mod uses it to register commands to set active
> handler, for example:
>
> parser.sh
> menu_viewer.text
> terminal_output.gfxterm

Great.

> 3, configfile now support an optional parameter to specify the script
> engine, for example:
>
> configfile /aa.cfg sh
>
> When configfile returns, the script engine would be restored to the
> previous value. This is useful for switching script engine. For
> example, you can parse a file in another language, then switch back to
> sh for the rest of grub.cfg.

I object to the syntax, but not to the idea. "configfile" is GRUB-specific, so 
it might be acceptable. But IIRC the underlying function is shared 
with "source", right? In Bourne Shell, "source FILE ARG" means that the file 
FILE is executed with a positional argument ARG. So it is not intuitive to 
specify a parser this way.

I proposed using a shebang some days ago. Was it so bad?

> 4, normal.mod set the default parser and menu viewer before parsing
> grub.cfg: parser.sh
> menu_viewer.text


Regards,
Okuji



  parent reply	other threads:[~2009-04-09 23:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30 17:41 [PATCH] Split of normal mode (version 2) Bean
2009-04-03 18:40 ` Yoshinori K. Okuji
2009-04-03 19:49   ` Bean
2009-04-03 20:12     ` Yoshinori K. Okuji
2009-04-03 22:19       ` phcoder
2009-04-03 23:02         ` Colin D Bennett
2009-04-05 14:23           ` Yoshinori K. Okuji
2009-04-04  5:06       ` Bean
2009-04-05 14:33         ` Yoshinori K. Okuji
2009-04-05 15:02           ` Bean
2009-04-05 15:43             ` Yoshinori K. Okuji
2009-04-06 16:39               ` Bean
2009-04-07  0:41                 ` Yoshinori K. Okuji
2009-04-09 23:49                 ` Yoshinori K. Okuji [this message]
2009-04-10  5:17                   ` Bean
2009-04-10 20:17                     ` Bean
2009-04-11  9:50                       ` Yoshinori K. Okuji
2009-04-11 14:03                         ` Bean

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=200904100849.57251.okuji@enbug.org \
    --to=okuji@enbug.org \
    --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.