On Fri, May 15, 2009 at 1:14 PM, Antonio Cárdenas wrote:
> Hi Professor Stein,
>
> I like Sage, it is a great project. I sent an email to the FSF about listing
> it in the high priority list:
> http://www.fsf.org/campaigns/priority.html
Thanks!
> They agree that Sage is a great and necessary pr
Hi Lucio,
In fluxbox, choose Sage off the menu. On a 1920x1240 (or so)
widescreen laptop, the terminal window might only use about 640x480
(or less?). it looks pretty tiny and then the fonts are barely
legible.
You can still read everything, but it would get old pretty quick. And
I couldn't s
Hi Rob,
the only issue that remains is the resolution you talked about.
When does it happen, at boot or during your sagelwlcd under fluxbox?
Greetings,
Lucio.
On Sat, May 9, 2009 at 5:26 PM, Lucio Lastra wrote:
> Hi Rob,
>
> I tried and already can add a "POWER OFF" option and "EXIT"
> will
> Oops, I mean C-q C-i
Hmm. What is M-; bound to for you? For me, it's `comment-dwim',
which is the greatest thing since sliced bread -- it really does do
what I mean! In a docstring, if you're on a line with non-comment
text, it adds a comment to the end of the line. Save for the space
On Fri, May 15, 2009 at 10:05 AM, Brian Granger wrote:
>
> That is exactly what Ondrej (he has done most of the work) and I are
In fact, it was William and Mike Hansen who did most of the work with
decoupling the notebook off Sage.
But it now works fine in SPD and everything builds nicely (in a
> > Here is my use case. I
> > like to have comments in my tests neatly aligned:
> >
> > sage: foo # todo: ...
> > sage: bar # done!
> > sage: ... # blah
> >
> > Since is not available for this in docstrings, I took the (bad)
> > habit of usi
> Hmm, probably my reason for having tabs is bad, and should be fixed in
> the first place by having the right feature.
Yes, this is not a good use for tabs :)
> Here is my use case. I
> like to have comments in my tests neatly aligned:
>
> sage: foo # todo: ...
> sage: ba
That is exactly what Ondrej (he has done most of the work) and I are
going with spdproject (Source Python Distribution):
http://code.google.com/p/spdproject/
We are just getting started, but we do have a base packages that includes:
numpy
scipy
ipython
sympy
the sage notebook
twisted/zope.inter
It would be nice if someone with an interest in qf would review #5954
and #6040. It gets the code up to 100% and improves various bits :)
Cheers,
Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from thi
On May 15, 1:57 am, "Dr. David Kirkby"
wrote:
Hi Dave,
> This might interest some.
>
> http://groups.google.co.uk/group/comp.soft-sys.math.mathematica/brows...
>
> where someone is questioning the commitment of Wolfram Research towards
> Solaris. There are currently no replies to it, but it w
On May 15, 2:47 am, Robert Bradshaw
wrote:
> On May 14, 2009, at 11:28 PM, mabshoff wrote:
> > Info like this should not go into trac, but on a wiki page. If you
> > want to see what has changed between revisions on the wiki it is
> > tedious at best.
I obviously meant trac being tedious.
On May 14, 2009, at 11:28 PM, mabshoff wrote:
> On May 14, 3:41 pm, Robert Bradshaw
> wrote:
>> On May 14, 2009, at 2:02 PM, Nicolas M. Thiery wrote:
>
>
>
>>> I am trying to keep the patch description on trac up-to-date
>>> (from the
>>> description in the patch itself):
>>
>>>http://sag
On Tue, Feb 24, 2009 at 12:07 PM, Mike Hansen wrote:
>
> On Tue, Feb 24, 2009 at 11:02 AM, Alex Clemesha wrote:
>> We are actively
>> building knoboo on Django,
>> so there may be added benefits from that one might need - but, the
>> Sage notebook is just way more usable right now.
>
> Is there
Hi Michael,
On May 15, 9:52 am, mabshoff wrote:
> I am not sure I understand the question, but there is no need to
> provide a diff or anything like that. It is sufficient just to put the
> modified files into the spkg. But it would be nice to have a diff of
> the original and the modified C-Mea
This might interest some.
http://groups.google.co.uk/group/comp.soft-sys.math.mathematica/browse_thread/thread/98221645e2cc7b5e?hl=en#
where someone is questioning the commitment of Wolfram Research towards
Solaris. There are currently no replies to it, but it will be
interesting if anyone fro
On May 15, 12:35 am, simon.k...@uni-jena.de wrote:
> Hi Michael,
>
> On May 15, 9:07 am, mabshoff wrote:
>
> > Your modifications must be GPL Compatible, i.e. either the GPL itself
> > or something like a 2 clause BSD.
>
> Sure, but this was my question: *How* do I make my modifications
> compa
Hi Michael,
On May 15, 9:07 am, mabshoff wrote:
> Your modifications must be GPL Compatible, i.e. either the GPL itself
> or something like a 2 clause BSD.
Sure, but this was my question: *How* do I make my modifications
compatible?
I mean, must I document somewhere what the exact changes are?
On May 14, 11:51 pm, "Nicolas M. Thiery"
wrote:
> On Thu, May 14, 2009 at 10:40:26PM -0700, mabshoff wrote:
> Note that I did not choose to go for Symmetrica in the first place!
> In MuPAD-Combinat, I already had done the work of replacing it
> whenever possible by lrcalc.
I looked at lrcal
On May 15, 12:00 am, Simon King wrote:
> Hi all!
>
> For my p-group cohomology spkg, I use some third party code. It is an
> old version of C-MeatAxe that we use for historic reasons; the code is
> shortened and extensively modified.
>
> As much as I understand, C-MeatAxe is under GPL. But I do
Hi all!
For my p-group cohomology spkg, I use some third party code. It is an
old version of C-MeatAxe that we use for historic reasons; the code is
shortened and extensively modified.
As much as I understand, C-MeatAxe is under GPL. But I don't know what
I must do concerning my modifications in
20 matches
Mail list logo
