On Fri, Aug 27, 2010 at 2:59 PM, Jeremy Bopp <jer...@bopp.net> wrote: > On 8/27/2010 1:28 PM, Tim Visher wrote: >> Hello Everyone, >> >> I recently switched from setting up environment variables within my >> bash_profile/bashrc file and instead started setting them on the box >> I'm on. This works great for PATH. In Windows I set the values to >> c:/whateverwhatever and then when my terminal fires up they get >> cygpathed (I'm assuming) into the right /usr/etcetcetc. >> Unfortunately, I'm observing no such behavior with the MANPATH. I >> can't see any difference between it and the PATH value so I was >> wondering if this was something that cygwin does intentionally. > > Cygwin only processes a handful of environment variables automatically > in the way you expect. They include PATH, HOME, TMP, and TEMP if my > memory serves correctly. Anything else you need to do for yourself. > > The problem is that there is no general way to know what environment > variables should be processed, so an explicit list must be created and > maintained. Apparently, a minimal set was chosen which is usually > sufficient to get you into a Cygwin environment at which point you can > selectively handle further processing as necessary. > > For defining MANPATH within Windows, you could just specify it as Cygwin > wants it unless you have some non-Cygwin programs which also need to use > MANPATH.
Thanks, Jeremy. That was basically the conclusion I'd come to before you mailed but it was good to have it confirmed. I've edited all the relevant PATHS and it all works now. -- In Christ, Timmy V. http://blog.twonegatives.com/ http://five.sentenc.es/ - Spend less time on e-mail -- 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
