On Tue, May 24, 2011 at 08:42:30PM +0200, Corinna Vinschen wrote: >On May 24 13:21, Christopher Faylor wrote: >> On Tue, May 24, 2011 at 09:19:08AM +0200, Corinna Vinschen wrote: >> >On May 23 15:33, Christopher Faylor wrote: >> >> On Mon, May 23, 2011 at 08:21:20PM +0200, Corinna Vinschen wrote: >> >> >IMHO it would be quite helpful if a setenv ("CYGWIN", ...) or putenv >> >> >("CYGWIN=...") would change the CYGWIN settings for the calling process >> >> >as well. >> >> >> >> Well, unless you make that change, all of the other Cygwin environment >> >> variables (not just "tty") need to be set before the first Cygwin >> >> process in a tree is started. Parsing the CYGWIN environment variable >> >> on the fly is trivial but I don't know for sure if there are some >> >> settings which only work right when set during program initialization. >> > >> >I had a quick look: >> > >> > "dosfilewarning" Sets a bool. Has immediate effect. >> > "envcache" Ditto. >> > "error_start" Sets a string. Has immediate effect. >> > "export" Sets a bool. Has effect on exec'ed child processes. >> > "glob" Sets two bools. Has effect on exec'ed child processes. >> > "proc_retry" Sets number. Has immediate effect. >> > "reset_com" Sets bool. Has immediate effect. >> > However, per the comment in fhandler_serial::open this >> > works around a problem in Windows 9x! Maybe we should >> > kill the setting? >> >> Yep. It's always fun to nuke those. > >Talking about nuking CYGWIN settings, I have at least two more candidates: > > "envcache" Did we ever had a problem which could be attributed > to this setting?
Don't think so. > "export" Does anybody really set CYGWIN settings in the registry? > Shouldn't we drop fetching CYGWIN settings from the registry > entirely? Every time this comes up I say "I do". The implementation allows you to set the CYGWIN environment variable on a per path basis. While it's not well advertised, I think it's still pretty useful. > "proc_retry" Does it really help? Yes. I actually implemented it for a customer so I'd rather not remove it. >Personally I would also remove "strip_title", "display_title", and >"upcaseenv", but that's just me. I'd be happy to remove strip_title and display_title. I thought that someone would complain if we didn'thave upcaseenv but I was wrong so I think that can go too. >> > "strip_title" and >> > "display_title" set bools. Has effect on exec'ed child processes. >> > "tty" Well... >> > "upcaseenv" Sets bool. Has effect on exec'ed child processes. >> > "winsymlinks" Sets bool. Has immediate effect. >> > >> >So, as far as I can tell, except for the "tty" setting everything else >> >would work nicely if set via setenv/putenv. >> >> Ok. No objections here. Do you want to do it or should I? > >No worries, just go ahead. Ok. I'll remove most of the above too. cgf