| To: | Don Cragun <dcragun@xxxxxxxxx> |
|---|---|
| Subject: | Re: Invalid shell assignments in environment |
| From: | Chet Ramey <chet.ramey@xxxxxxxx> |
| Date: | Thu, 02 Jul 2009 16:18:10 -0400 |
| Cc: | austin-group-l@xxxxxxxxxxxxx, chet.ramey@xxxxxxxx |
| Organization: | ITS, Case Western Reserve University |
| References: | <200907012242.n61MgCCp020103@xxxxxx> <4A4C2005.6030402@xxxxxx> <4a4c81a6.2tWl4Z9DpJUyvd+z%Joerg.Schilling@xxxxxx> <200907021327.n62DRe5k029384@xxxxxx> <20090702143325.GA5491@xxxxxx> <4A4CCA35.6070009@xxxxxx> <4A4CCBE1.7020801@xxxxxx> <20090702150847.GA6190@xxxxxx> <090702183047.AA87319.SM@xxxxxx> <4858.76.191.129.144.1246561262.squirrel@xxxxxx> |
Don Cragun wrote: > In practice, most system do not have a problem here. Yes, I understand. The majority of the systems I care about :-) don't have a problem with this. We can safely say that shell variable names are composed of uppercase letters, lowercase letters, digits, and the underscore as they appear in ASCII. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRU chet@xxxxxx http://cnswww.cns.cwru.edu/~chet/ |
| Previous by Date: | Re: [Aardvark Bugs 0000115]: Email notifications do not report what wasupdated, Mark Brown |
|---|---|
| Next by Date: | Re: Invalid shell assignments in environment, Chet Ramey |
| Previous by Thread: | Re: Invalid shell assignments in environment, Don Cragun |
| Next by Thread: | Re: Invalid shell assignments in environment, Chet Ramey |
| Indexes: | [Date] [Thread] [All Lists] |