Hi,
I added the new now-done Russian Sage quickref that Anna Clawson made here:
http://wiki.sagemath.org/quickref
-- William
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
--
You received this message because you are subscribed to the Go
On Monday, March 3, 2014 10:24:57 AM UTC-8, kcrisman wrote:
>
>
>
> On Monday, March 3, 2014 10:48:47 AM UTC-5, rjf wrote:
>>
>> I think there is poor usability of a menu that pops up like this -- where
>> the
>> menu changes depending upon the selection. When the menu is standardized
>> as in
On Saturday, 1 March 2014 19:39:13 UTC-7, jason wrote:
>
> I just updated the sagecell spkg:
>
> http://boxen.math.washington.edu/home/jason/sagecell-spkg/sagecell-2014-03-01.spkg
>
>
> I also updated my sage sagecell branch to 6.1.1.
>
> Jason
>
>
>
Doing exactly same things as before, I cann
So should I use a different function to save on the local version? Is this a
bug?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegr
On Mon, Mar 3, 2014 at 10:40 AM, Volker Braun wrote:
> On Monday, March 3, 2014 6:20:27 PM UTC, kcrisman wrote:
>>
>> a lot of users on Mac/Windows move programs around all the time.
>
>
> Try moving your MS Office install on Windows .Good luck.
Volker's right. Also with Mac's many programs can
On Monday, March 3, 2014 6:20:27 PM UTC, kcrisman wrote:
>
> a lot of users on Mac/Windows move programs around all the time.
>
Try moving your MS Office install on Windows .Good luck.
On Mac one does essentially what I'm proposing. Because of the utter lack
of any package management system, you
On Monday, March 3, 2014 10:48:47 AM UTC-5, rjf wrote:
>
> I think there is poor usability of a menu that pops up like this -- where
> the
> menu changes depending upon the selection. When the menu is standardized
> as in file-edit-view etc, and the sub-menus are always the same (but
> with
On Sunday, March 2, 2014 11:11:10 AM UTC-5, Volker Braun wrote:
>
> On Sunday, March 2, 2014 11:33:22 AM UTC+1, Jeroen Demeyer wrote:
>
>> The problem is that Sage cannot know in advance that you will *not* move
>> the Sage tree.
>
>
> Neither does any other software. If you move an installed pr
I think there is poor usability of a menu that pops up like this -- where
the
menu changes depending upon the selection. When the menu is standardized
as in file-edit-view etc, and the sub-menus are always the same (but with
perhaps
some options dimmed), the user can learn from past exposure
On 3/2/14, 4:45, Harald Schilly wrote:
Second, functionalities are not discoverable. In Sage there is more
and more a trend to group top-level functions by a topic, e.g. someone
types "graphs.[TAB]" and the tab key expands a list of functions only
for graphs. Additionally, once you have construct
There was some attempt to replace it with Jenkins at SD56, but I don't know
how how far that progressed. Since the changeset information is now easily
accessible through git it would make sense to replace it with a more
run-of-the-mill continuous integration tool.
On Monday, March 3, 2014 10
Hello,
it seems that the patchbot has not really digested the git transition. I
would be happy to see it back, as it was very useful in the development
process in the mercurial era.
To modify the patchbot, you have to clone from here
https://github.com/robertwb/sage-patchbot
and then propose
I've upgraded our OSX buildbot slave to 10.9.2 and it works fine. Your
xcode install is broken, try reinstalling or ask Apple for help. Expected
output is
$ as -v
Apple Inc version cctools-846.2.4, GNU assembler version 1.38
--
You received this message because you are subscribed to the Googl
13 matches
Mail list logo
