On Jun 8, 2012, at 11:30 AM, Martin Albrecht wrote: > Hi, > > I am not sure where to send these, but I figured the following would > be rather nice:
Here is fine, or you could open tickets either on trac (cc me--iandrus) or open issues on https://bitbucket.org/gvol/sage-mode/ > - Sage mode (at least in my setup) is bound to one Sage instance. But > if one plays with SPKGs one may have many. Hence, if sage-mode could > figure out the copy of Sage to use automatically, or I could set it > once per session, that'd be great. I'm not sure how much work this would take. It might be as simple as setting `sage-command` to a buffer local variable when you visit a file. Certainly you could set it globally in `sage-mode-hook` and the last one would win. I'm most worried about how this would interface with the sage shell since you wouldn't want to send Sage 5 code to a Sage 4 shell. I think python-mode.el supports multiple versions of pythons runnings, but to my knowledge neither the current python.el, nor fgallina's, supports this. > - sage-test is awesome. Can we perhaps add something like: > fix-this-doctest-failure? It would replace the expected line with the > line one got. It would help to fix the trivial stuff. Of course, it > should be handled with care etc. but it would make things nicer. That's a good idea. We already have `sage --fixdoctests` so this would just be a more granular form of that. I created issue on bitbucket if you want to follow them. I'll try to get to them (especially the second) soon, but I can't make any promises. There is some cleanup that I need to do first. https://bitbucket.org/gvol/sage-mode/issue/3/support-multiple-versions-of-sage https://bitbucket.org/gvol/sage-mode/issue/2/add-sage-fix-doctest-at-point -Ivan -- 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
