You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working up a simple emacs recipe for fully syntactically valid source files arranged in blocks. jupytext would be ideal for conversion back and forth to notebook format. The idea is to use multi-line strings or block comments to wrap markdown blocks. This makes language servers, linters, etc. much happier. One interesting idea would be to allow slightly different header formats, somewhat like percent, but serving double duty as the nested outline section headers used in emacs, e.g.:
# * A Top-level cellmy_code()
# ** A second level cell [markdown]r'''- A list'''# *** A 3rd level cellprint('3rd!')
Is there a convenient way to customize jupytext to target such a style?
One other thought regarding multi-line string cell_markers for Python. Ideally the starting marker would specify a raw string — r''' — so that checkers don't look inside the string and complain about invalid escape sequences (in LaTeX fragments, for example).
The text was updated successfully, but these errors were encountered:
I've been working up a simple emacs recipe for fully syntactically valid source files arranged in blocks. jupytext would be ideal for conversion back and forth to notebook format. The idea is to use multi-line strings or block comments to wrap markdown blocks. This makes language servers, linters, etc. much happier. One interesting idea would be to allow slightly different header formats, somewhat like percent, but serving double duty as the nested outline section headers used in emacs, e.g.:
Is there a convenient way to customize jupytext to target such a style?
One other thought regarding multi-line string
cell_markers
for Python. Ideally the starting marker would specify a raw string —r'''
— so that checkers don't look inside the string and complain about invalid escape sequences (in LaTeX fragments, for example).The text was updated successfully, but these errors were encountered: