Pat LeSmithe wrote:
> This is now v2 at
> http://trac.sagemath.org/sage_trac/ticket/8168
Much appreciated, thanks!
Best regards, xtian
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+un
I'm just a dumb user ;-) and no Sage system coder, so I don't know
which implications my suggestions may have on Sage integrity,
but anyway:
On 1 Feb., 16:48, Pat LeSmithe wrote:
> On 02/01/2010 07:15 AM, xtian wrote:
> > On 1 Feb., 11:12, Pat LeSmithe wrote:
> >
The problem is not as simple as I thought at first. After digging for
a while, I think I found the constraint which leads to the behavior I
observed:
On 1 Feb., 11:12, Pat LeSmithe wrote:
> On 01/27/2010 02:31 PM, xtian wrote:
> > In the Sage 4.3.1 interpreter, an attached file get
Nick Alexander wrote:
> On 28-Jan-10, at 1:38 PM, xtian wrote:
> > On 28 Jan., 22:32, xtian wrote:
> >> [...]
> >> This leaves me with one last thing to do for now: giving up.
> > ...which is not a big thing, I should add. No complaint or stuff
> > fr
On 28 Jan., 22:32, xtian wrote:
> [...]
> This leaves me with one last thing to do for now: giving up.
...which is not a big thing, I should add. No complaint or stuff
from my side. And thanks for all the fish. :-)
(Bye)^2, xtian
--
To post to this group, send an email to sage
ire 'python). Result: emacs21 whining "Symbol's function
definition
is void: define-button-type".
This leaves me with one last thing to do for now: giving up.
Just 2 pence, xtian
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
p expertise
is almost non-existent). I keep getting errors there. I'm not
depending on sage-mode, so no worries (as far as I'm concerned).
Thanks anyway!
xtian
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage
ot much of an elisp expert as to see the
problem here. Could be an api change in rx between emacs21
and emacs22 or something. The wrong-number-of-arguments
error message points into this direction (just guessing).
I got a report that with 'emacs22 --debug-init', there is no problem
showing a
2
My Sage installation is self-compiled from source.
4.3 had been upgraded from earlier versions.
For 4.3.1, I used a freshly extracted source tree.
Best regards, xtian
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
There's a ticket related to the issue already:
http://trac.sagemath.org/sage_trac/ticket/6989
I missed that when searching for existing tickets.
Best regards, xtian
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
Just for the record,
On 27 Jan., 14:35, xtian wrote:
> If a list of vectors gets passed as an argument to
> sage.plot.line.line(), the entries' types are changed
> from 'vector' to 'tuple' by the call to the
> line() function.
> [...]
Environment info
ge session and the type change will show.
Best regards, xtian
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
David Kirkby schrieb:
> On Oct 13, 9:28 am, Christian Hilberg wrote:
> > Hi,
> > I'm experiencing instruction set issues with the SAGe Linux i686
> > binary tarball from
> [...]
> This issue comes up many times. I wonder if it would be preferable to
> not include the sse2 instruction set. I don
13 matches
Mail list logo
