All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] doc: document config_directory and config_file variables
Date: Sat, 7 Nov 2015 23:09:08 +0300	[thread overview]
Message-ID: <563E5A64.80601@gmail.com> (raw)
In-Reply-To: <563E564F.6000207@gmx.fr>

07.11.2015 22:51, Arbiel (gmx) пишет:
> Hi
>
> There seems to be other variables and command parameters which lack
> documentation.
>
> Here is a list of such variables found in my grub.cfg files (I have
> discarded "save_env"ed variables, obviously environment variables) and
> which are not set in the environment block
>
> ${feature_menuentry_id}
> ${boot_once}
> $feature_all_video_module
> $feature_default_font_path
> $feature_platform_search_hint
> $feature_timeout_style

I do not not think any of them need to be documented in user manual. 
Features are of interest to developers to ensure backward compatibility; 
users start off with a given version and need not usually care if it 
works in earlier ones. $boot_once is internal implementation variable 
that is of no interest to anyone and its purpose is obvious by reading 
script.

It's fine to describe them in developers documentation of course, but so 
far nobody volunteered to maintain it.

> $match
>
> As the names suggest, these variables could be distribution specific
> (Ubuntu). What do you think ?
>
> undocumented command parameter : --hint (command search), and some other
> --hint.something which I haven't been able to localise just now.
>

Which command?

> I found in my grub.cfg file a "hwmatch" command which is not defifed as
> a function. Is this a undocumented grub command ? Its result may well
> the  $match variable.
>

Both are Ubuntu (or may be Debian) specific.



  reply	other threads:[~2015-11-07 20:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 10:21 [PATCH] doc: document config_directory and config_file variables Andrey Borzenkov
2015-11-07 13:45 ` Vladimir 'phcoder' Serbinenko
2015-11-07 19:51 ` Arbiel (gmx)
2015-11-07 20:09   ` Andrei Borzenkov [this message]
2015-11-07 22:58     ` Arbiel (gmx)
2015-11-08  6:55       ` 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=563E5A64.80601@gmail.com \
    --to=arvidjaar@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.