Environment variable mixing when starting non-cygwin GVIM from within cygwin terminal?

[Christopher Faylor]

On Mon, Feb 06, 2012 at 01:04:28PM -0800, reckoner wrote:
>Hi,
>
>I usually start the non-cygwin gvim.exe via the rxvt cygwin console 
>doing something like:
>
>% gvim filename.py
>
>the problem is that, when inside GVIM, when I do:
>
>:py print os.environ['PATH']
>
>I see a lot of cygwin paths which messes up the Python path that GVIM 
>wants to use. Is there a way to start gvim.exe so that this doesn't 
>happen? Note that I can avoid this situation by starting GVIM in a plain 
>vanilla CMD window, or from a standard window shortcut, instead of using 
>the cygwin terminal.

Why not just set PATH to whatever you want prior to running your windows
version of gvim?  You could even make an alias:

alias gvim='PATH=WHATEVER /path/to/your/gvim'

--
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