From: SourceForge.net <no...@so...> - 2006-05-03 21:06:22
|
Bugs item #1481218, was opened at 2006-05-03 18:13 Message generated for change (Settings changed) made by haible You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1481218&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: None Status: Open Resolution: None Priority: 3 Submitted By: Jörg Höhle (hoehle) >Assigned to: Sam Steingold (sds) Summary: initial -M device-relative pathname on win32 Initial Comment: Unlike the DIR command, CLISP does not recognize the device-relative syntax D:lispinit.mem to load from D's current directory. C:\Programme\CLISP>d: D:\hoehle>c:lisp.exe -M c:lispinit.mem c:lisp.exe: operating system error during load of initialization file `c:lispinit.mem' GetLastError() = 0x2 (ERROR_FILE_NOT_FOUND): The system cannot find the file specified. D:\hoehle>dir c:lispinit.mem Datenträger in Laufwerk C: hat keine Bezeichnung. Verzeichnis von C:\Programme\CLISP 01.07.2005 18:11 1.664.696 lispinit.mem 1 Datei(en) 1.664.696 Bytes An absolute pathname works (no surprise): D:\hoehle>c:lisp.exe -M c:\Programme\CLISP\lispinit.mem i i i i i i i ooooo o ooooooo ooooo ooooo I I I I I I I 8 8 8 8 8 o 8 8 Local drives or Samba mounted drives make no difference. The machine is MS-Windows-2000 SP4. ---------------------------------------------------------------------- Comment By: Bruno Haible (haible) Date: 2006-05-03 23:05 Message: Logged In: YES user_id=5923 Could it be a bug in the function real_path (w32shell.c) ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1481218&group_id=1355 |