On Mon, Jun 15, 2009 at 6:03 AM, Marshall Hampton wrote:
>
> I care about the polymake spkg, and I know a few users who do too. It
> would be nice to fix it; the last time I tried to install it I got
> some errors I didn't understand at all so I'm not sure what exactly
> the problem is. Its prob
On Mon, Jun 15, 2009 at 9:06 AM, maxthemouse wrote:
>
>
>>
>> > Another thing that does not work is "sage -
>> > lisp" which gave the clisp prompt. I found this rather convenient
>> > since I could just use the clisp within sage. Is there any plan/
>> > interest to switch the this lisp interface t
>
> > Another thing that does not work is "sage -
> > lisp" which gave the clisp prompt. I found this rather convenient
> > since I could just use the clisp within sage. Is there any plan/
> > interest to switch the this lisp interface to ecl? Does ecl use
> > readline?
>
> For now you can at lea
I care about the polymake spkg, and I know a few users who do too. It
would be nice to fix it; the last time I tried to install it I got
some errors I didn't understand at all so I'm not sure what exactly
the problem is. Its probably out of date anyway, so it might be best
to start from scratch
On Sun, Jun 14, 2009 at 6:55 PM, maxthemouse wrote:
>
>
>
> On Jun 14, 3:57 pm, William Stein wrote:
>> Hi,
>>
>> In case anybody cares about the optional Sage polymake spkg, I've
>> moved it from optional to experimental, since it doesn't work at all.
>> See below. Also, note that the fricas
On Jun 14, 3:57 pm, William Stein wrote:
> Hi,
>
> In case anybody cares about the optional Sage polymake spkg, I've
> moved it from optional to experimental, since it doesn't work at all.
> See below. Also, note that the fricas spkg no longer works (unless
> the user has clisp systemwide)
