From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1GYTPZ-000714-Tj for mharc-grub-devel@gnu.org; Fri, 13 Oct 2006 16:13:41 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GYTPX-00070O-Vk for grub-devel@gnu.org; Fri, 13 Oct 2006 16:13:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GYTPV-0006yF-50 for grub-devel@gnu.org; Fri, 13 Oct 2006 16:13:39 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GYTPV-0006y4-0L for grub-devel@gnu.org; Fri, 13 Oct 2006 16:13:37 -0400 Received: from [212.85.152.101] (helo=kotoba.storever.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GYTY0-0003tQ-QV for grub-devel@gnu.org; Fri, 13 Oct 2006 16:22:25 -0400 Received: from kotoba.oasis.nexedi.com (kotoba.oasis.nexedi.com [212.85.152.101]) by kotoba.storever.com (Postfix) with ESMTP id 645CE3CC46AC8 for ; Sat, 14 Oct 2006 00:44:47 +0200 (CEST) Received: from [??1] (localhost [127.0.0.1]) by kotoba.storever.com (Postfix) with ESMTP id 4168A3CC46AC6 for ; Sat, 14 Oct 2006 00:44:47 +0200 (CEST) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Fri, 13 Oct 2006 22:13:34 +0200 User-Agent: KMail/1.8.2 References: <87fye2swwa.fsf@xs4all.nl> <200610132132.11614.okuji@enbug.org> <87d58wro1g.fsf@xs4all.nl> In-Reply-To: <87d58wro1g.fsf@xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610132213.34486.okuji@enbug.org> X-Bogosity: No, tests=bogofilter, spamicity=0.029281, version=0.17.2 Subject: Re: Scripting (IMPORTANT!) X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 20:13:40 -0000 On Friday 13 October 2006 21:52, Marco Gerards wrote: > > I thought the same thing before, but I didn't, because the effect of > > setting the root device has a different meaning, that is, to set a boot > > device for the chainloader. Besides this, the root variable is very > > similar to the concept of "current working directory" in Unix. So I > > wouldn't object strongly, even if you change it this way. > > I think it makes more sense when scripting. I also think it is easier > for users to deal with. I don't know. I leave the decision to you. > > BTW the Intel's EFI Shell uses an option to a command to enable a pager. > > This way might be more convenient than a variable. Or a pipe? I think a > > pipe sounds overkill, though. > > Well, I made this a variable because we wanted variables instead of > commands when possible. Exactly. > Well, $1, $2, etc makes more sense to me as well. But it doesn't > describe what really happens, although the user might not be concerned > with this. I will start a discussion on this if it causes problems. I guess this wouldn't be a big problem, since most users wouldn't use this feature. > >> ===== > >> for > >> ===== > >> > >> The for command can be used to iterate over a set of data. I don't > >> like the idea of implementing this *exactly* like in bash. Personally > >> I am thinking of the following syntax: > >> > >> Iterating over files: > >> for x in (hd0,3)/foo/* ; do commands ; done > > > > How is this different from BASH? The asterisk is interpreted as a > > wildcard, and this is not a part of "for" in BASH. > > You removed the relevant context. Right, GRUB has no wildcard. I > don't really understand what you mean. I meant that the asterisk is not a part of a description for "for". > > This sounds too much for me. How about supporting a subset of "set" in > > BASH? For example, set -d and set +d. The default can be set -d. > > What do you mean by "this"? I assume you mean -e instead of -d? I > hope you can check what you really mean, a -d does not exist. Oops. Yes, I meant -e instead. Okuji