On Jun 12 15:11, Ray Donnelly wrote: > Ok, We're back to asking for a plugin with a clearly defined interface for > env. var and path translation; despite LRNs reasonable objections I think > it might be the only acceptable solution? > > .. that way we can continue to speculate (as MSYS always has) about what's > a path and what isn't and also use the cygwin.dll unmodified. > > Otherwise we're at an impasse.
First, may I politely ask, if this is really necessary, or if everybody thinks it's necessary just because the old MSYS did so. Does anybody have a real world example which requires this, and isn't easily fixed by using cygpath at the crucial stage? Corinna -- Corinna Vinschen Cygwin Maintainer Red Hat ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
