-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Further improve the double percent format #89
Comments
mwouts
added a commit
that referenced
this issue
Oct 2, 2018
mwouts
added a commit
that referenced
this issue
Oct 2, 2018
mwouts
added a commit
that referenced
this issue
Oct 2, 2018
mwouts
added a commit
that referenced
this issue
Oct 5, 2018
mwouts
added a commit
that referenced
this issue
Oct 5, 2018
mwouts
added a commit
that referenced
this issue
Oct 6, 2018
mwouts
added a commit
that referenced
this issue
Oct 10, 2018
mwouts
added a commit
that referenced
this issue
Oct 10, 2018
mwouts
added a commit
that referenced
this issue
Oct 10, 2018
mwouts
added a commit
that referenced
this issue
Oct 10, 2018
mwouts
added a commit
that referenced
this issue
Oct 10, 2018
mwouts
added a commit
that referenced
this issue
Oct 10, 2018
Available in v0.8.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The double percent format seems to have a very nice potential as a standard text representation for Jupyter notebooks. It is already understood by many editors, some of which support other languages than Python.
Below is a list of desirable improvements for
jupytext
's implementation of the format:jupyter nbconvert
. Currently most editors that can read the double percent scripts already do that, i.e. cells may start withIn [21]
, etc.%
in it), and cell depth is stored in another metadata.;
or;;
for scheme or lisp,//
for c++, etc).The text was updated successfully, but these errors were encountered: