All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Born <futur.andy@googlemail.com>
To: GRUB2 Devel <grub-devel@gnu.org>
Subject: Re: [bug #27710] variable type not exported into new context
Date: Sun, 06 Dec 2009 23:57:53 +0100	[thread overview]
Message-ID: <4B1C36F1.4000602@googlemail.com> (raw)
In-Reply-To: <20091015-153848.sv74720.97143@savannah.gnu.org>

As of r1917 grub_env_context_open still doesn't mark exported variables 
as global in the new context.
Attached patch exports them with grub_env_export in the new context.

Andreas Born schrieb:
> URL:
>   <http://savannah.gnu.org/bugs/?27710>
>
>                  Summary: variable type not exported into new context
>                  Project: GNU GRUB
>             Submitted by: shador
>             Submitted on: Do 15 Okt 2009 15:38:48 GMT
>                 Category: Terminal
>                 Severity: Major
>                 Priority: 5 - Normal
>               Item Group: Software Error
>                   Status: None
>                  Privacy: Public
>              Assigned to: None
>          Originator Name: 
>         Originator Email: 
>              Open/Closed: Open
>          Discussion Lock: Any
>                  Release: 
>                  Release: SVN
>          Reproducibility: Every Time
>          Planned Release: None
>
>     _______________________________________________________
>
> Details:
>
> A variable created and exported afterwards, isn't marked 'export' after a new
> context was created by issuing configfile. Thus if you issue another time
> configfile the variable is unset.
> This means recursive menus deeper than 2 menus are not possible by loading
> another configfile.
>
> Example:
> set blub=blob
> export blub
> configfile <file>
> configfile <file>
> echo $blub
> => nothing, blub was unset after the second configfile (prefix also so
> everything fails).
>
> Workaround:
> In every new context (-> every .cfg file) (re)export the variable (and
> prefix, root).
>
> Attached is a patch which marks variables copied into the new context again
> 'export' preventing breakage of prefix and root.
>
>
>
>     _______________________________________________________
>
> File Attachments:
>
>
> -------------------------------------------------------
> Date: Do 15 Okt 2009 15:38:48 GMT  Name: export-context.diff  Size: 359B  
> By: shador
>
> <http://savannah.gnu.org/bugs/download.php?file_id=18886>
>
>     _______________________________________________________
>
> Reply to this item at:
>
>   <http://savannah.gnu.org/bugs/?27710>
>
> _______________________________________________
>   Nachricht geschickt von/durch Savannah
>   http://savannah.gnu.org/
>
>   




       reply	other threads:[~2009-12-06 22:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091015-153848.sv74720.97143@savannah.gnu.org>
2009-12-06 22:57 ` Andreas Born [this message]
2009-12-15 18:38   ` [bug #27710] variable type not exported into new context Andreas Born

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=4B1C36F1.4000602@googlemail.com \
    --to=futur.andy@googlemail.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.