Fwd: Patch for customizing Allegro temp file and directory
Dear Slime Maintainers, Please consider applying the attached patch, which affects swank-allegro.lisp and allows customization of the temporary directory for Allegro CL. It turns out that Allegro's (system:temporary-directory) [which is the default directory used by system:make-temp-file-name] can sometimes get confused on Windows in situations such as with certain network filesystem configurations. We will follow up with Franz to understand in more detail what can cause the confusion, but in any case I think it will be useful to be able to customize the location of Slime's temporary files without modifying Slime sources. -- My Best, Dave Cooper, Genworks Support
Dave Cooper <gendl@genworks.com> writes:
Dear Slime Maintainers,
Please consider applying the attached patch, which affects swank-allegro.lisp and allows customization of the temporary directory for Allegro CL. It turns out that Allegro's (system:temporary-directory) [which is the default directory used by system:make-temp-file-name] can sometimes get confused on Windows in situations such as with certain network filesystem configurations.
We will follow up with Franz to understand in more detail what can cause the confusion, but in any case I think it will be useful to be able to customize the location of Slime's temporary files without modifying Slime sources.
Hi Dave, Sorry for the delay in answering this, I've recently been bitten by the same problem and I've found that setting SYS:*TEMPORARY-DIRECTORY* to NIL (or to something else) unconfuses Allegro CL. As soon as it has been set once, SYS:MAKE-TEMP-FILE-NAME is should never be confused again, and should follow the algorithm described in: http://franz.com/support/documentation/current/doc/operators/system/temporar... So swank-allegro.lisp should function correctly and the variables you suggest are provided by Allegro themselves. Did you follow up with Franz on this problem? João
[Slime maintainers: please disregard my original patch submission on this thread (if you haven't already!)] Dear João, Thank you for the followup. We have not yet followed up on this with Franz, because we been unable to reliably replicate the issue at our site. If you are able to replicate it or describe how to replicate it, would you mind sending a report to Franz? Best Regards, Dave On Tue, Mar 18, 2014 at 7:15 AM, João Távora <joaotavora@gmail.com> wrote:
Dave Cooper <gendl@genworks.com> writes:
Dear Slime Maintainers,
Please consider applying the attached patch, which affects swank-allegro.lisp and allows customization of the temporary directory for Allegro CL. It turns out that Allegro's (system:temporary-directory) [which is the default directory used by system:make-temp-file-name] can sometimes get confused on Windows in situations such as with certain network filesystem configurations.
We will follow up with Franz to understand in more detail what can cause the confusion, but in any case I think it will be useful to be able to customize the location of Slime's temporary files without modifying Slime sources.
Hi Dave,
Sorry for the delay in answering this, I've recently been bitten by the same problem and I've found that setting SYS:*TEMPORARY-DIRECTORY* to NIL (or to something else) unconfuses Allegro CL. As soon as it has been set once, SYS:MAKE-TEMP-FILE-NAME is should never be confused again, and should follow the algorithm described in:
http://franz.com/support/documentation/current/doc/operators/system/temporar...
So swank-allegro.lisp should function correctly and the variables you suggest are provided by Allegro themselves.
Did you follow up with Franz on this problem?
João
joaotavora@gmail.com (João Távora) writes:
Sorry for the delay in answering this, I've recently been bitten by the same problem and I've found that setting SYS:*TEMPORARY-DIRECTORY* to NIL (or to something else) unconfuses Allegro CL.
Hi again, SOrry for the noise, but this turned out to be bogus. Allegro is still confused, so either Franz fixes it or just uses Luís idea. João
2014-03-18 19:57 GMT+00:00 João Távora:
SOrry for the noise, but this turned out to be bogus. Allegro is still confused, so either Franz fixes it or just uses Luís idea.
The binding of *default-pathname-defaults* in swank-allegro.lisp's swank-compile-string doesn't seem sensible (i.e. it contains a name or a type), or even necessary. Maybe it affects how the temporary directory is determined, or subsequent pathname merging. It's the only backend where this is done. I have no idea why. Best regards, Paulo Madeira
On Thu, Feb 20, 2014 at 9:20 PM, Dave Cooper <gendl@genworks.com> wrote:
Please consider applying the attached patch, which affects swank-allegro.lisp and allows customization of the temporary directory for Allegro CL. It turns out that Allegro's (system:temporary-directory) [which is the default directory used by system:make-temp-file-name] can sometimes get confused on Windows in situations such as with certain network filesystem configurations.
Since that issue will affect every use of SYS:TEMPORARY-DIRECTORY, not just SLIME, have you considered placing an FWRAPPER around it? (In any case, this issue rings a bell; I'll investigate if and how we get around it at work, tomorrow.) Cheers, -- Luís Oliveira http://kerno.org/~luis/
participants (4)
-
Dave Cooper -
joaotavora＠gmail.com -
Luís Oliveira -
Paulo Madeira