On 6-Mar-09, at 8:30 AM, Nicolas M. Thiery wrote:
>
> Hi Nick!
>
> On Thu, Feb 19, 2009 at 01:15:54PM -0800, Nick Alexander wrote:
>> sage-mode-0.5.2 is up at http://wiki.sagemath.org/sage-mode. It has
>> brief docs (very brief!) but you can now use sage-view-
>> {enable,disable}-inline-{
Hi Nick!
On Thu, Feb 19, 2009 at 01:15:54PM -0800, Nick Alexander wrote:
> sage-mode-0.5.2 is up at http://wiki.sagemath.org/sage-mode. It has
> brief docs (very brief!) but you can now use sage-view-
> {enable,disable}-inline-{plots,output} to toggle bits of behaviour.
> In additi
found another little bug. The function sage-view-disable-inline-plots
works fine when called interactively (after run-sage, that is) -- but
in my case it does not work when placed in sage-startup-hook as
suggested on the wiki page ! i mean i have
(add-hook 'sage-startup-hook 'sage-view-always 'sa
here's another trick i use, by the way. It simply attaches the current
buffer to sage, so you just need to go C-x C-s on your file in order
to send everything :
(defun sage-attach-current-buffer ()
"attach current .sage file"
(interactive)
(process-send-string (get-buffer "*SAGE-main*")
On Feb 23, 2:43 am, Pierre wrote:
Hi,
> brilliant ! 0.5.2 works really well ! the toggle idea is very nice : i
> sense that i'm going to use both inline and external plots.
>
> if i may add something to the list of bug reports, i'd say that python-
> send-region and python-send-defun apparent
brilliant ! 0.5.2 works really well ! the toggle idea is very nice : i
sense that i'm going to use both inline and external plots.
if i may add something to the list of bug reports, i'd say that python-
send-region and python-send-defun apparently do nothing. When i want
to send a part of a file
> Now I agree. The difficult part is having three latex processes with
> three sentinels.
That's it!
I shifted to the version shipped with sage-mode-0.5.2 this morning. I'll
be away for a couple of days, so you'll hopefully get the multiple
outputs stuff in the middle of next week.
Regards,
On 19-Feb-09, at 9:54 AM, Pierre wrote:
>
>> Let me make sure I know the situation: you have applied that small
>> patch, you have installed sage-mode-0.5.1 (from the wiki), and you
>> are
>> running Aquamacs?
>
> exactly, but in reverse order (applying the patch came last)
>
>> (I haven't tri
>> Not so easy to fix...
>
> With the original code, yes. With the newer code that accumulates
> output and post-processes it, not so hard.
Now I agree. The difficult part is having three latex processes with
three sentinels.
Nick
--~--~-~--~~~---~--~~
To pos
On 19-Feb-09, at 8:56 AM, Matthias Meulien wrote:
>
>> Would that were true! There are plenty of bugs left, maybe you will
>> help me fix them :)
>
> I am currently working on `the multiple output bug'. More precisely,
> in case we run the following code, three overlays should be inserted
> in
On 19-Feb-09, at 9:54 AM, Pierre wrote:
>
>> Let me make sure I know the situation: you have applied that small
>> patch, you have installed sage-mode-0.5.1 (from the wiki), and you
>> are
>> running Aquamacs?
>
> exactly, but in reverse order (applying the patch came last)
That's fine.
>> (
> Let me make sure I know the situation: you have applied that small
> patch, you have installed sage-mode-0.5.1 (from the wiki), and you are
> running Aquamacs?
exactly, but in reverse order (applying the patch came last)
>(I haven't tried it with aquamacs.) Also, the
> inline equation
> Would that were true! There are plenty of bugs left, maybe you will
> help me fix them :)
I am currently working on `the multiple output bug'. More precisely,
in case we run the following code, three overlays should be inserted
in the sage buffer:
m = Matrix(QQ, 5)
m.randomize()
for i in ra
On 19-Feb-09, at 2:24 AM, Pierre wrote:
>
> hello all,
>
> i've posted this in sage-support with no luck. Strikes me it might be
> for sage-devel...
>
> I've installed the latest package for emacs, now with sage-view. Wow !
> very very cool, all the bugs are gone.
Would that were true! There a
> It is also quite early on the west
> coast, so he might reply soonish. Nick uses MacOSX, so he might be
> able to narrow it down quickly.
He just woke up!
Let me make sure I know the situation: you have applied that small
patch, you have installed sage-mode-0.5.1 (from the wiki), and you are
On Feb 19, 5:40 am, Pierre wrote:
> > * run
Hi Pierre,
> > hg_sage.apply("http://trac.sagemath.org/sage_trac/attachment/
> > ticket/5147/trac_5147-plot-output-filename.patch")
>
> i've tried that. It didn't seem to complain too much, though i did get
> the message:
>
> WARNING:
> Make su
> * run
>
> hg_sage.apply("http://trac.sagemath.org/sage_trac/attachment/
> ticket/5147/trac_5147-plot-output-filename.patch")
i've tried that. It didn't seem to complain too much, though i did get
the message:
WARNING:
Make sure to create a ~/.hgrc file:
---
On Feb 19, 5:20 am, Pierre wrote:
Hi Pierre,
> > > (...) Use sage-view in an inferior sage buffer to have all your output
> > > latexed and your plot commands appear inline in the inferior sage
> > > buffer -- after you apply the patch at
> > >http://trac.sagemath.org/sage_trac/ticket/5147.
>
> > (...) Use sage-view in an inferior sage buffer to have all your output
> > latexed and your plot commands appear inline in the inferior sage
> > buffer -- after you apply the patch at
> >http://trac.sagemath.org/sage_trac/ticket/5147.
>
> I've not tried it. But it seems to be the thing your ar
Hi Pierre,
> I've installed the latest package for emacs, now with sage-view. Wow !
> very very cool, all the bugs are gone.
Thanks to Nick Alexander's great work!
> could i combine this behavior with the nice formulae of sage-view ?
> this would be the definite death of the notebook for me (no
20 matches
Mail list logo
