No, I can't.
$ foo%%="bar"
foo%%=bar: command not found
Or better said not in the normal way
$ set foo%%=bar
--
Mit freundlichen Grüßen
Lorenz Bucher
TechConnect GmbH
Im Auftrag der/on behalf of
Rohde & Schwarz GmbH & Co. KG
Postfach 80 14 69 • 81614 München
Mühldorfstraße 15 • 81671 München
Telefon: (089) 4129-15684
Mail: lorenz.bucher....@rohde-schwarz.com
Internet: www.rohde-schwarz.com
Von: Chet Ramey <chet.ra...@case.edu>
An: lorenz.bucher....@rohde-schwarz.com, wool...@eeg.ccf.org,
Kopie: bug-bash@gnu.org, "Eduardo A. Bustamante López"
<dual...@gmail.com>, chet.ra...@case.edu
Datum: 10/16/2014 03:09 PM
Betreff: Re: Issue with Bash-4.3 Official Patch 27
Gesendet von:
bug-bash-bounces+lorenz.bucher.ext=rohde-schwarz....@gnu.org
On 10/15/14, 1:49 PM, lorenz.bucher....@rohde-schwarz.com wrote:
> But anyway.
> In my opinion I should trust a shell not violating their own rules and
be
> able to import their own variables.
That's not the issue. The shell can import variables like that just fine,
as evidenced by exported functions actually working. The question is
whether or not `export' lets you set and export non-identifiers. It does
and should not.
> So the % character should be allowed to be used in variable names.
No, shell variable names should continue to be shell identifiers. You
can already use `%' (any character, really) in environment variable
names.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu
http://cnswww.cns.cwru.edu/~chet/
