I see imagine kluge that could make things work under Windows:
create a temporary .bat file then execute it with cmd /c foo.bat
Unhappily, I don't have a Windows machine to test on.
Alternatively, fixing SBCL so that :force-shell t works.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
Hi,
I tried this expression on sbcl windows x86-64.
(uiop/run-program:run-program "c:/windows/system32/tree /?" :output :string)
I notice the result changed after commit 94e9f4c0.
on windows platform run-program with :output is :string and :force-shell is
T,the result was already broken before th
SANO Masatoshi reports that uiop:run-program broke on SBCL/Windows at
some point between 3.1.3 and 3.1.5.
Can someone with SBCL and Windows help me debug that?
A trace of functions in uiop/run-program and the functions in sb-ext
that appear in that file,
using ASDF on 3.1.3 and on 3.1.5, on some f
Dear Robert,
> I've made some more progress with a Maxima extension for ASDF
> (attached).
This looks much more like it. Congrats!
> At this point the only thing I wish I could change (and this is a
> minor item) is that output file paths are something like
> $HOME/.cache/common-lisp/.
> I'm
On Wed, Sep 23, 2015 at 1:10 PM, Faré wrote:
> >>: Faré
>
> >> when asdf-ecl was initially written, its load-fasl-op was intended
> >> as the default way to load a system. Because of implementation bugs
> >> revealed as ASDF improved its testing, this feature was disabled at
> >> some point while
Hey everybody,
I've made some more progress with a Maxima extension for ASDF
(attached). At this point it works pretty much as expected, for the
simple examples I've tried. I think you should be able to use in
Maxima like this: load("maxima_asdf.lisp"); asdf_load("foo"); to load
foo.asd, which may
> "Pascal" == Pascal J Bourguignon writes:
Pascal> Raymond Toy
Pascal> writes:
>>> "Far" == Far writes:
>>
Far> test and file a bug against CLISP. Maybe some day CLISP will have new
Far> maintainers who'll fix it. Anyone who uses logical pathnames DESERVES
>>: Faré
>> when asdf-ecl was initially written, its load-fasl-op was intended
>> as the default way to load a system. Because of implementation bugs
>> revealed as ASDF improved its testing, this feature was disabled at
>> some point while developing ASDF 3.1. Now that these implementation
>> bug
Dear François-René,
On Wed, Sep 23, 2015 at 1:21 AM, Faré wrote:
> Dear Daniel, dear Jean-Claude,
>
> when asdf-ecl was initially written, its load-fasl-op was intended
> as the default way to load a system. Because of implementation bugs
> revealed as ASDF improved its testing, this feature was
