grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Arbiel (gmx)" <arbiel.perlacremaz@gmx.fr>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Setting config_directory to prefix at grub launch time
Date: Fri, 15 Jan 2016 22:40:47 +0100	[thread overview]
Message-ID: <5699675F.4010709@gmx.fr> (raw)
In-Reply-To: <5699287D.4080409@gmail.com>

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



Le 15/01/2016 18:12, Andrei Borzenkov a écrit :
> 15.01.2016 17:18, Arbiel (gmx) пишет:
>> However, I confirm config_directory is not listed in the output of the
>> set command.
> That's correct. config_directory is set when executing config file and
> unset when processing is completed.
I understand the processing of a file to come to its end when grub
displays its menu.
> When you are in CLI, there is no
> config file, so it is not set. Each configfile command is executed in
> own environment which is destroyed when it is finished. You may have
> multiple (also nested) configfile invocations.  What would you set it
> to?
I'm just happy with that. I only made a wrong deduction based on the
fact that I did not see config_directory in the set's output.
> config_directory has no meaningful value outside of configfile
> processing.
That's clear.
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]

  reply	other threads:[~2016-01-15 21:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 10:16 Setting config_directory to prefix at grub launch time Arbiel (gmx)
2016-01-15 10:22 ` Andrei Borzenkov
2016-01-15 11:32   ` Arbiel (gmx)
2016-01-15 14:18     ` Arbiel (gmx)
2016-01-15 17:12       ` Andrei Borzenkov
2016-01-15 21:40         ` Arbiel (gmx) [this message]
2016-01-16  6:25           ` Andrei Borzenkov

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=5699675F.4010709@gmx.fr \
    --to=arbiel.perlacremaz@gmx.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).