From: Mirko V. <mir...@gm...> - 2008-11-12 22:18:48
|
On Tue, Nov 11, 2008 at 2:35 PM, Sam Steingold <sd...@gn...> wrote: > Mirko Vukovic wrote: >> >> On Tue, Nov 11, 2008 at 12:57 PM, Sam Steingold <sd...@gn...> wrote: >>> >>> I just discovered (and, hopefully, fixed) an apparent bug in makemake.in >>> which >>> should have caused a line >>> (setq *device-prefix* "") >>> to be appended to config.lisp, resulting in clisp not handling properly >>> pathnames like "c:/foo/bar". >>> what do cygwin clisp users see for >>> *device-prefix* ==> ? >>> (truename "c:/autoexec.bat") ==> ? >>> (or some other existing file on c:)? >>> what if you do >>> (setq *device-prefix* "cygdrive")? >>> does CVS head treat such pathnames better ootb? >>> thanks. >> >> Is this useful? > > yes, very! > thanks! > >> CL-USER> *device-prefix* >> "" >> CL-USER> (truename "c:/autoexec.bat") >> #P"/c/autoexec.bat" >> CL-USER> (setq *device-prefix* "cygdrive") >> "cygdrive" >> CL-USER> (truename "c:/autoexec.bat") >> #P"/cygdrive/c/autoexec.bat" >> CL-USER> >> >> I have c: mounted as /c. > > did you do something special to accomplish that or is this the new cygwin > default behavior? > if you do not do this, does (truename "c:/autoexec.bat") fail? > > > Sam, I don't think I did anything special. I am not sure what you are driving at, so I could be missing your point. Mirko |