-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Can't define new commands for LaTeX #490
Comments
I believe this is fixed in master, and will be released with notebook-4.1 ( |
I just hit this issue and it's a big problem for me. Will 4.1. be released soon? I am using conda for notebook and would prefer to keep it that way. |
We should confirm that this is fixed @SylvainCorlay is saying it isn't... |
Fixed and closing... |
Yes, we are getting it ready for release in the next week or so. |
I was having this bug also with ipython notebook, i fixed it reinstalling everything with conda, but installing the jupyter notebook directly from the repo, and everything is working nice, :). |
@juangil Thanks for the report verifying that installing Jupyter notebook from the repo has the LaTeX working nicely. We hope you are enjoying Jupyter notebook too. 📖 😄 |
it works in live notebook, but it fails with nbconvert: I'm using master branch (for both notebook and nbconvert) for a simple macro define: this generates the following log: """
""" |
to let nbconvert generate pdf, we need to define using however this requires enabling a mathjax extension: TeX: { |
Issue #349 was closed, but I still keep getting the same problems: defining new commands in markdown cells with
$\newcommand{}{}$
does not seem to work.I'm using jupyter 4.0.6 ((
jupyter --version
), installed with Anaconda, on OS X. The cell were the new command is defined has the same strange output and the cells were the newly defined macro is used are not rendered; I just get the command name in red, like an error.Here is a sample screenshot:
The text was updated successfully, but these errors were encountered: