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
When you set let g:jupytext_filetype_map = {'md:myst': 'markdown'} let g:jupytext_extension_map = {'md:myst': 'md'} let g:jupytext_fmt = 'md:myst'
the new format isn't taken into account and opening a file yields an error about unrecognized format despite jupytext --to md:myst working
A clear and concise description of what the bug is.
Diagnostics
vim --version: NVIM v0.4.4
Operating system information (e.g. uname -a): SMP Debian 5.14.6-3 (2021-09-28) x86_64 GNU/Linux
Does converting the notebook to/from ipynb with jupytext on the command line work? Yes
Does it work when you set g:jupytext_command in ~/.vimrc to be the exact some jupytext that you used manually, with the exact same version of Python? Yes
The text was updated successfully, but these errors were encountered:
There is no g:jupytext_extension_map. This is not a user-configurable mapping. The keys in s:jupytext_extension_map should be all the formats that jupytext supports, and if jupytext gains new formats, that dict should be extended accordingly. I'm not really following the development of jupytext, but I'd merge PR's that extend s:jupytext_extension_map with new formats.
When you set
let g:jupytext_filetype_map = {'md:myst': 'markdown'} let g:jupytext_extension_map = {'md:myst': 'md'} let g:jupytext_fmt = 'md:myst'
the new format isn't taken into account and opening a file yields an error about unrecognized format despite
jupytext --to md:myst
workingA clear and concise description of what the bug is.
Diagnostics
vim --version
: NVIM v0.4.4Operating system information (e.g.
uname -a
): SMP Debian 5.14.6-3 (2021-09-28) x86_64 GNU/Linuxpython --VV
: Python 3.9.7 (default, Sep 24 2021, 09:43:00)Are you using Anaconda? No
Does converting the notebook to/from ipynb with
jupytext
on the command line work? YesDoes it work when you set
g:jupytext_command
in~/.vimrc
to be the exact somejupytext
that you used manually, with the exact same version of Python? YesThe text was updated successfully, but these errors were encountered: