[sage-devel] Re: [ANN] sage-mode-0.6

2009-05-12 Thread Dan Drake
On Tue, 12 May 2009 at 05:05PM -0700, Nicolas M. Thiery wrote: > - Is there general support in emacs for switching between two modes, > depending on whether one is in the code or in comments? I very much > like the rst-mode of emacs, and in the long run it would be great > to edit the doctest

[sage-devel] Re: [ANN] sage-mode-0.6

2009-05-12 Thread Nick Alexander
> Yippee! All of those are serious time savers! Thanks! > >> Beta testers, please let me know what problems you have. >> I felt like I added a lot of requested features this iteration, so >> keep them coming. > > I will :-) > > An to start with: > > - C-C C-j seems to get confused by tabs in the i

[sage-devel] Re: [ANN] sage-mode-0.6

2009-05-12 Thread Jason Grout
Jason Grout wrote: > Nicolas M. Thiery wrote: >> >> - Is there general support in emacs for switching between two modes, >>depending on whether one is in the code or in comments? I very much >>like the rst-mode of emacs, and in the long run it would be great >>to edit the doctests in

[sage-devel] Re: [ANN] sage-mode-0.6

2009-05-12 Thread Jason Grout
Nicolas M. Thiery wrote: > > > - Is there general support in emacs for switching between two modes, >depending on whether one is in the code or in comments? I very much >like the rst-mode of emacs, and in the long run it would be great >to edit the doctests in rst-mode and the code

[sage-devel] Re: Sage 4.0.a0 status update

2009-05-12 Thread William Stein
2009/5/11 mabshoff : > > Ok, no 4.0.a0 yet, but it should drop fairly soon. An update of what > is going on: > >  * 75% coverage - we are already close at 74.4% or so and the pynac > symbolics switch will get us past 75%. There is also a bunch of code > in trac that should increase coverage even f

[sage-devel] Re: [ANN] sage-mode-0.6

2009-05-12 Thread Nicolas M. Thiery
On Mon, May 11, 2009 at 10:22:32PM -0700, Nick Alexander wrote: > > I am pleased to announce the release of sage-mode-0.6, the all- > singing, all-dancing sage development Emacs environment. As always, > you can get it from http://wiki.sagemath.org/sage-mode. But now... > it's in the optio

[sage-devel] Re: name of wiki pages

2009-05-12 Thread David Joyner
On Tue, May 12, 2009 at 5:29 PM, mabshoff wrote: > > Hi, > > this isn't against David, it just annoys me to no end that people do > this: This has come up before, but I consider it *completely useless* > when someone opens a page named > >  http://wiki.sagemath.org/extra%20documentation%20%28for%

[sage-devel] Re: name of wiki pages

2009-05-12 Thread William Stein
On Tue, May 12, 2009 at 2:29 PM, mabshoff wrote: > > Hi, > > this isn't against David, it just annoys me to no end that people do > this: This has come up before, but I consider it *completely useless* > when someone opens a page named > >  http://wiki.sagemath.org/extra%20documentation%20%28for%

[sage-devel] name of wiki pages

2009-05-12 Thread mabshoff
Hi, this isn't against David, it just annoys me to no end that people do this: This has come up before, but I consider it *completely useless* when someone opens a page named http://wiki.sagemath.org/extra%20documentation%20%28for%20the%20standard%20components%20of%20SAGE%29 since no one can

[sage-devel] Re: 3.4.2 64 bit MacIntel 10.5 binary with only *one* doctest failure

2009-05-12 Thread mabshoff
On May 12, 10:37 am, William Stein wrote: > 2009/5/12 mabshoff : > I can resolve the failure in gen.pyx easily: Just completely delete > the finitefield_init function!     Well, nuking functionality is always a solution ;) >  This pari function has always been > flakie, IMHO, and is used n

[sage-devel] Re: 3.4.2 64 bit MacIntel 10.5 binary with only *one* doctest failure

2009-05-12 Thread William Stein
2009/5/12 mabshoff : > > Hello folks, > > due to Martin Albrecht tracking down the evasive libSingular issue > (turns out it was a linker oddity due to static libs being linked > multiple times into an extension in case you care) I have build a > 3.4.2 binary with various fixes and posted it at >

[sage-devel] Re: accessors for FreeAlgebraElement

2009-05-12 Thread Nick Alexander
On 12-May-09, at 7:56 AM, Florent Hivert wrote: > > Dear William, > >> FreeAlgebraElement was written in 2005, and nobody has worked on it >> since. >> Maybe now it is your turn. > > Or my student's :). That was my intention ! The obvious question is > now the > naming convention. It se

[sage-devel] Re: accessors for FreeAlgebraElement

2009-05-12 Thread William Stein
On Tue, May 12, 2009 at 7:56 AM, Florent Hivert wrote: > >      Dear William, > >> FreeAlgebraElement was written in 2005, and nobody has worked on it since. >> Maybe now it is your turn. > > Or my student's :). That was my intention ! The obvious question is now the > naming convention. It seems

[sage-devel] Re: accessors for FreeAlgebraElement

2009-05-12 Thread Florent Hivert
Dear William, > FreeAlgebraElement was written in 2005, and nobody has worked on it since. > Maybe now it is your turn. Or my student's :). That was my intention ! The obvious question is now the naming convention. It seems to me that we should stick as close as possible to polynomials: s

[sage-devel] Re: accessors for FreeAlgebraElement

2009-05-12 Thread William Stein
On Tue, May 12, 2009 at 12:50 AM, Florent Hivert wrote: > >      Dear All, > > It seems that FreeAlgebraElement is missing some accessors: > It is very easy to create elements: >    sage: sage: A.=FreeAlgebra(ZZ,3) >    sage: bla = -x+3*y*z >    sage: bla >    -x + 3*y*z > but I can't find any wa

[sage-devel] accessors for FreeAlgebraElement

2009-05-12 Thread Florent Hivert
Dear All, It seems that FreeAlgebraElement is missing some accessors: It is very easy to create elements: sage: sage: A.=FreeAlgebra(ZZ,3) sage: bla = -x+3*y*z sage: bla -x + 3*y*z but I can't find any way to get some information on an element (except for printing it of cour

[sage-devel] 3.4.2 64 bit MacIntel 10.5 binary with only *one* doctest failure

2009-05-12 Thread mabshoff
Hello folks, due to Martin Albrecht tracking down the evasive libSingular issue (turns out it was a linker oddity due to static libs being linked multiple times into an extension in case you care) I have build a 3.4.2 binary with various fixes and posted it at http://sage.math.washington.edu/