-
Notifications
You must be signed in to change notification settings - Fork 51
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
Problem with single quote in markdown cell #54
Comments
I can't reproduce the problem. Probably you are using different version of markdown-mode. Nevertheless, what you can do is to stop using markdown mode in markdown cell. (setq ein:mumamo-markdowncell-mode 'text-mode) Syntax highlighting of multiple language in a single is difficult problem. EIN is relying on the ability of MuMaMo and it looks like it is impossible to stop fontification mechanism. |
I don't think I have MuMaMo installed. Maybe I should. From: Takafumi Arakaki <[email protected]mailto:[email protected]> I can't reproduce the problem. Probably you are using different version of markdown-mode. Nevertheless, what you can do is to stop using markdown mode in markdown cell. (setq ein:mumamo-markdowncell-mode 'text-mode) Syntax highlighting of multiple language in a single is difficult problem. EIN is relying on the ability of MuMaMo and it looks like it is impossible to stop fontification mechanism. — |
Ah, I see. So whole buffer is parsed by python-mode. Probably that is not a good default. |
I just installed nxhtml (which comes with mumamo) and restarted Emacs. Now when I ask to create a new notebook, I get the following error backtrace: ''' ''' From: Takafumi Arakaki <[email protected]mailto:[email protected]> Ah, I see. So whole buffer is parsed by python-mode. Probably that is not a good default. � |
It looks like the version problem again. What version of mumamo you are using? You can check it by Also, please check the call signature of (mumamo-find-next-chunk-values AFTER-CHUNK) |
Mine also says it's 0.91, and the signature reports (mumamo-find-next-chunk-values AFTER-CHUNK FROM AFTER-CHANGE-MAX Search forward for start of next chunk. For the first chunk AFTER-CHUNK is nil. Otherwise the values in stored in AFTER-CHUNK From: Takafumi Arakaki <[email protected]mailto:[email protected]> It looks like the version problem again. What version of mumamo you are using? You can check it by mumamo:version. Mine is 0.91. Also, please check the call signature of mumamo-find-next-chunk-values. I have this: (mumamo-find-next-chunk-values AFTER-CHUNK) — |
OK, that means I can't rely on mumamo:version to identify the actual version. How did you install nxhtml? It should work if you install the latest developmental version. I installed nxhtml from https://github.com/emacsmirror/nxhtml using el-get. I guess easiest way to fetch it from zeroein/nxhtml/ since you already tried zeroein. |
Thanks. Now it works – mostly. As I navigate around the notebook, I get frequent warnings: Warning (mumamo-per-buffer-local-vars): Already 'permanent-local t: buffer-file-name From: Takafumi Arakaki <[email protected]mailto:[email protected]> OK, that means I can't rely on mumamo:version to identify the actual version. How did you install nxhtml? It should work if you install the latest developmental version. I installed nxhtml from https://github.com/emacsmirror/nxhtml using el-get. I guess easiest way to fetch it from zeroein/nxhtml/ since you already tried zeroein. — |
Yes, sometime mumamo is too noisy. I found it is especially annoying, even unable to use, when used with python-mode.el. What python-mode are you using? python.el or python-mode.el? |
Python-mode. As you say, the errors (and associated buffer) pop up so often that it's almost unusable... From: Takafumi Arakaki <[email protected]mailto:[email protected]> Yes, sometime mumamo is too noisy. I found it is especially annoying, even unable to use, when used with python-mode.el. What python-mode are you using? python.el or python-mode.el? — |
I guess the problem is in combination of mumamo.el and python-mode.el, as it works OK when using python.el. Sorry, I can't give you a solution here. Both mumamo.el and python-mode.el are too big to find a workaround. Probably you should open an issue ticket in python-mode.el or switch to python.el. |
I added #58 for the issue with python-mode.el. Please comment there if you find something. |
I found a simple workaround: (setq python-saved-check-command nil) Mumamo seems to be referencing a variable that's defined in python.el but not in python-mode.el. From: Takafumi Arakaki <[email protected]mailto:[email protected]> I guess the problem is in combination of mumamo.el and python-mode.el, as it works OK when using python.el. Sorry, I can't give you a solution here. Both mumamo.el and python-mode.el are too big to find a workaround. Probably you should open an issue ticket in python-mode.el or switch to python.el. — |
python-saved-check-command is defined only in the old python.el. I wonder why it is referenced from python-mode.el. I guess a better way to fix is to remove the following line from the mode definition (make-local-variable 'python-saved-check-command) Anyway, thanks for the info. |
I added this in wiki tips, thanks https://github.com/tkf/emacs-ipython-notebook/wiki/Tips |
I have a single quote (used as an apostrophe) in the text in one of my markdown cells. Unfortunately, this seems to cause everything after it in the entire buffer to be highlighted as though inside a string. Of course, I could just use a different character, but shouldn't syntax highlighting be turned off in markdown cells? (Or is this just not possible?)
The text was updated successfully, but these errors were encountered: