incompatible environment variable names

[Andrey Repin]

Greetings, Nellis, Kenneth!

> Well, *somehow* it got into the Cygwin environment, and cygwin.bat directly
> invokes bash, so I interpret this as bash creating the Cygwin environment.
> Where is the hole in this logic?

Even windows itself creates environment variables inaccessible through CMD.
Still, they are available to running programs.
On another edge, TC(ex. 4NT) shell support variables that not actually
environmental, rather - status variables related to current shell state or
recently happened events.
There's no logic, just usefulness.


--
WBR,
 Andrey Repin (anrdaemon@freemail.ru) 04.08.2010, <23:18>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple