GNU GRUB - Bugs: bug #27710, variable type not exported into...
You are not allowed to post comments on this tracker with your current authentication level.
bug #27710: variable type not exported into new context
Submitter: | Andreas Born <shador> | ||
Submitted: | Thu 15 Oct 2009 03:38:48 PM UTC | ||
Category: | Terminal | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | Fixed | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Closed | Release: | Bazaar - trunk |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
Attached Files
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2009-12-21 | phcoder | Status | None | Fixed | |
Open/Closed | Open | Closed | |||
2009-10-15 | shador | Attached File | - | Added export-context.diff, #18886 |
Powered by Savane 3.13-f8d8.
Corresponding source code
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.