On Mon, Feb 07, 2011 at 03:36:26PM -0700, Gary Furash wrote: > Has anyone written anything into their bash profile or whatever that goes > through each windows environment variable currently extant, and resets them > via CYGPATH > > Before, @ start of .bashrc > ETC=C:\WINDOWS\ETC > > After run of .bashrc > ETC=`$(cygpath -u '$ETC')`; EXPORT ETC (--> /cygpath/c/windows/etc) > > Or something like that. So, by the time you hit your cygwin prompt all your > environment variables are already cleaned up.
I have seen the need to take windows paths conversion into account only when dealing with Java apps from within cygwin: e.g. a tomcat appserver, where the catalina.sh converts cygwin paths into windows ones before sending them to the JVM, that doesn't understand them. Other than that, I fail to understand what is the use for this. Could you please elaborate on a use case for such a configuration? Also note that, following your example, you can still reach /cygpath/c/windows/etc without converting anything. -- Huella de clave primaria: 0FDA C36F F110 54F4 D42B D0EB 617D 396C 448B 31EB
signature.asc
Description: Digital signature