On Apr 3 16:51, Corinna Vinschen wrote: > On Apr 3 12:37, Thomas Wolff wrote: > > This would mean you could no longer effectively invoke the cygwin.bat > > or cygwinutf.bat scripts within a Windows console and get the proper > > charset? That would not be good. > > No, that's not right. The locale setting for the console would last > from the first Cygwin parent process started in a console, up to the > last Cygwin child process called by another Cygwin process, without > invoking another native Windows process in the interim. Every closed > Cygwin process tree works on it's own console-wise, for all practical > purposes. Start cmd.exe from your bash, and then start bash again, then > these two bashes will not share certain information which is inherited > to Cygwin child processes, inclduing console settings. > > Again, the setting of the console would depend on the > LC_ALL/LC_CTYPE/LANG setting when you start the first Cygwin process of > a Cygwin process tree in that console. It would last for all Cygwin > processes within the same process tree.
This approach is now implemented in 1.7.0-46. Please give it a try. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/