X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.9 required=5.0 tests=AWL,BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,TW_YG,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4C780B13.8050807@bopp.net> References: <4C780B13 DOT 8050807 AT bopp DOT net> From: Tim Visher Date: Mon, 30 Aug 2010 10:53:29 -0400 Message-ID: Subject: Re: MANPATH not being cygpathed like PATH is? To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Fri, Aug 27, 2010 at 2:59 PM, Jeremy Bopp 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. =C2=A0This works great for PATH. =C2=A0In Windows I set the valu= es 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. =C2=A0I >> 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. =C2=A0They include PATH, HOME, TMP, and TEMP if my > memory serves correctly. =C2=A0Anything 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. =C2=A0Apparently, 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. --=20 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