Re: [sage-devel] Re: sage vs jupyter notebooks

Most of the issues I ran into are fixed (by lack of knowledge for markdown arrays and by Volker's work for Cython cells). Though >> * export is broken on my Sage install (in whatever format) >> > > Do you have pandoc installed? I do have pandoc installed and it is not the problem. The Jupyter

[sage-devel] Re: sage vs jupyter notebooks

Hi Vincent, I would add to your list: * when exporting to pdf, the LaTeX format of the output cells is lost (cf. https://groups.google.com/d/msg/sage-support/Pt_r9Ct-31w/MWkRz1DVBwAJ) * the menu of JSMol 3D plots is not accessible Best wishes, Eric. -- You received this message because you

Re: [sage-devel] Re: sage vs jupyter notebooks

Thanks Volker. In general, Jupyter uses github-flavored markdown, which supports tables and many other things: https://help.github.com/articles/organizing-information-with-tables/, for example. Jason On Thu, May 5, 2016 at 2:56 PM Volker Braun wrote: > A %%cython cell magic for commandline and

[sage-devel] Re: sage vs jupyter notebooks

A %%cython cell magic for commandline and Jupyter notebook is now at http://trac.sagemath.org/ticket/20562 (needs review) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

[sage-devel] Re: sage vs jupyter notebooks

Some of your complaints are just how the commandline currently works... On Thursday, May 5, 2016 at 2:46:10 PM UTC+2, vdelecroix wrote: > > * tab completion with jokers not supported (i.e. "*prime") > There is wildcard search: sage: *le_prim*? [ENTER] next_probable_prime > * the markdow

[sage-devel] Re: sage vs jupyter notebooks

See also https://groups.google.com/forum/#!topic/sage-support/E4jCF1mDRJE and perhaps comb through https://groups.google.com/forum/#!topic/sage-devel/8erxWppKxXM in case there are things you missed there (notably different interact syntaxes, I guess?). Thanks for starting this process. For li