[bug #36404] Colons in environment variable identifiers are unreadable

[Chris Trenkamp]

URL:
  <http://savannah.gnu.org/bugs/?36404>

                 Summary: Colons in environment variable identifiers are
unreadable
                 Project: GNU GRUB
            Submitted by: christrenkamp
            Submitted on: Sat 05 May 2012 01:49:54 AM 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: Bazaar - trunk
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

If an environment variable has a colon in its identifier, it will be
inaccessible when attempting to read it.

For example, after the user runs 'net_bootp', the environment variable
'net_pxe:dhcp_boot_file' will be set.  If the user attempts to read it with
echo '${net_pxe:dhcp_boot_file}', the command will return these errors:
error: $.
error: syntax error.
error: Incorrect command.
error: syntax error.

I've tried various ways to read these variable, but can't find one that works.
 I know these variables were meant to be read-only, which is probably why
there's a colon in the identifier, but it would be extremely useful to be able
to read them.





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?36404>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/