On Sunday, October 23, 2016 at 10:37:34 PM UTC, v_...@ukr.net wrote:
>
> On Sat, 22 Oct 2016 13:18:12 -0700 (PDT)
> Volker Braun > wrote:
>
> > Thats definitely a SageNB bug, though afaik nobody is maintaining
> > that. My recommendation would be to use "sage --notebook=jupyter"
> > instead.
On Sat, 22 Oct 2016 13:18:12 -0700 (PDT)
Volker Braun wrote:
> Thats definitely a SageNB bug, though afaik nobody is maintaining
> that. My recommendation would be to use "sage --notebook=jupyter"
> instead.
>
Hello!
I think, I have fixed this bug. At least, the Notebook does what I
need in
Here a very similar topic is being discussed, with more possibilities to
look at:
https://groups.google.com/d/msg/sage-devel/GSlGERRFe30/py52lp5uAgAJ
On Saturday, October 22, 2016 at 9:55:20 PM UTC, v_...@ukr.net wrote:
>
> On Sat, 22 Oct 2016 13:18:12 -0700 (PDT)
> Volker Braun > wrote:
>
> >
On Sat, 22 Oct 2016 13:18:12 -0700 (PDT)
Volker Braun wrote:
> Thats definitely a SageNB bug, though afaik nobody is maintaining
> that. My recommendation would be to use "sage --notebook=jupyter"
> instead.
>
Perhaps I could try to do that. Is there some guide on replacing the
Sage Notebook ser
Thats definitely a SageNB bug, though afaik nobody is maintaining that. My
recommendation would be to use "sage --notebook=jupyter" instead.
On Saturday, October 22, 2016 at 6:12:03 PM UTC+2, v_...@ukr.net wrote:
>
> Hello!
> I use the Sage Notebook on my server with Sage v.7.4. And each ti
