From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: adrian15sgd@gmail.com
Subject: Re: How one is supposed to write kind-of-library cfg files?
Date: Sun, 16 Mar 2014 09:49:55 +0400 [thread overview]
Message-ID: <20140316094955.05162a53@opensuse.site> (raw)
In-Reply-To: <532526C0.2090808@gmail.com>
В Sun, 16 Mar 2014 05:21:20 +0100
adrian15 <adrian15sgd@gmail.com> пишет:
> El 16/03/14 04:49, adrian15 escribió:
> > ( Using 2.02~beta2-7 from Debian Unstable )
> >
> > I have tried to write some cfg files to kind of organise them as
> > libraries but it does not work as expected.
> >
> > It seems as the sourced cfg files are being interpreted.
>
> I have managed to write a minimal working example. It would seem that
> the problem is having a function inside another function.
>
>
> Is it perhaps not officially supported?
>
Correct, in grub grammar functions cannot be nested.
prev parent reply other threads:[~2014-03-16 5:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 3:49 How one is supposed to write kind-of-library cfg files? adrian15
2014-03-16 4:21 ` adrian15
2014-03-16 5:49 ` Andrey Borzenkov [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=20140316094955.05162a53@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=adrian15sgd@gmail.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.