Header cells in Jupyter notebooks have been around a very long time (since essentially the beginning?). Years ago there was talk of deprecating them in lieu of just using Markdown header syntax in markdown cells. There aren't officially supported TOC or section-structuring features in the notebook. We may see more section-structuring features in the notebook going forward, though I don't know of anyone that has definite plans to work on it right now.
You can convert a notebook to tex using nbconvert, and you can even write latex in the notebook "raw" cells and have it output as part of the latex in a conversion. And there's no technical problem that I know if in doing something like sagetex using Jupyter kernels to give you the computation engine of Jupyter inside of TeX. What version of the Jupyter notebook is in Sage? I'd be surprised if it didn't have header cells. Jason On Fri, Jan 5, 2018 at 2:55 PM Dima Pasechnik <dimp...@gmail.com> wrote: > > > On Friday, January 5, 2018 at 12:46:16 PM UTC, Erik Bray wrote: > >> On Wed, Jan 3, 2018 at 2:47 PM, Emmanuel Charpentier >> > <emanuel.c...@gmail.com> wrote: >> > The documentation I referenced shows the presence of specific tools in >> their >> > implementation (specialized buttons, menus items, etc...) that seem to >> be >> > necessary for cross-referencing and auto-TOC. The "Header cells" seem >> to be >> > distinct from Markdown cells, code cells and raw cells. >> > >> > As far as I can tell, this is not available in "our" Jupyter. >> >> I'll have to take a closer look, but I'm still confused because >> "header cells" have been in the notebook going way back (since early >> versions of IPython Notebook). The cross-referencing and TOC stuff >> I'm less sure about. >> >> > I'm not sanguine about this enhancement : >> > >> > It certainly can be useful for heavy Jupyter users. >> > OTOH, it is also a form of "LaTeX envy"... >> > >> > I see more and more proposals to add LaTeX-like features to Markdown >> (such >> > as citation management, cross-referencing, indexing,....). But Markdown >> was >> > not created to be a LaTeX replacement, and these various proposals are >> > problem-specific kludges, mutually inconsistent and, IMNSHO, not up to >> the >> > standard proposed by LaTeX. >> > >> > I see these "enhancements" as a way to avoid the Matterhorn-like >> learnng >> > curve of LaTeX ; but I think that, in the long term, the larger >> investment >> > on LaTeX yelds a better ROI. The key point is, of course "in the long >> term" >> > : someone not planning to publish extensively might use Jupyter as a >> way to >> > meet a specific, one-time requirement (e. g. graduating) ; however, >> someone >> > planing to have to publish more than once or twice is probably better >> off >> > learning LaTeX which, as a scientific document preparation system, has >> not >> > yet been superseded (after about 30 years... !). >> >> I agree with all in theory. Though as I once learned, in an >> embarrassing manner, one of the first times I taught Software >> Carpentry to an audience that was not just astronomers/physicists, >> outside those fields and mathematics LaTeX is *not* de facto. >> > > Considering that Apple added a quite complete LaTeX support to Pages > (their presentations editor) > and iBooks Author (e-books writing tool) we'll hopefully see a wider use > of LaTeX > soon... > > > >> >> Yes, maybe scientists in life science, social science, etc. should >> also learn LaTeX but for many of those fields it's not nearly as >> common and there's maybe far less ROI there. >> >> > In other words, "heavy Jupyter use" is a bit of an oxymoron in my eyes >> (or, >> > at least, a misguided choice).But I might be missing a point, hence my >> > question. >> >> Maybe, but it's a whole new world... >> >> Best, >> E >> >> >> > Le mardi 2 janvier 2018 15:50:18 UTC+1, Erik Bray a écrit : >> >> >> >> On Tue, Dec 26, 2017 at 5:27 PM, Emmanuel Charpentier >> >> <emanuel.c...@gmail.com> wrote: >> >> > This question on ask.sagemath.org made me search Google about >> something >> >> > called "Header cells". I found such a thing in the Jupyter >> documentation >> >> > at >> >> > Bryn Mawr College. >> >> > >> >> > It seems to me that this is a site-specific extension, not something >> >> > standard, but I do not know how to find something authoritative >> about >> >> > what >> >> > is "standard" in Jupyter... >> >> >> >> I'm not sure what you mean. Header cells are a normal part of the >> >> notebook. As the name suggests it's just a special cell type for >> >> section headers in the notebook. You can also make headers by making >> >> a normal markdown cell and putting in markdown-formatted headers, but >> >> I think the point of header cells is that they are more inherently >> >> part of the structure of the notebook itself, independent of the types >> >> of cells following the header. So the header cell can be moved around >> >> relative to other cells and the notebook can keep track of it as part >> >> of its structure, if that makes sense. >> >> >> >> > It also seems to give some interesting possibilities : >> >> > cross-referencing, >> >> > automatic numbering, auto-table of contents. >> >> > >> >> > Do you think that this (or something like this) could be useful in >> our >> >> > Jupyter notebook ? >> >> >> >> You could do this in any Jupyter notebook I think. >> >> >> >> Best, >> >> Erik >> > >> > -- >> > 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+...@googlegroups.com. >> > To post to this group, send email to sage-...@googlegroups.com. >> > > Visit this group at https://groups.google.com/group/sage-devel. >> > For more options, visit https://groups.google.com/d/optout. >> > -- > 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...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- 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...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
