Non-python syntax highlighting disabled

[fonnesbeck]

In the current notebook master running on OS X 10.11.4 (Python 3.5.1), non-Python kernels do not have syntax highlighting enabled. Examples for the R and Julia kernels are depicted below:

R

Julia

System information:

Python 3.5.1 |Continuum Analytics, Inc.| (default, Dec 7 2015, 11:24:55)
[GCC 4.2.1 (Apple Inc. build 5577)]

Kernel: R version 3.2.5 (2016-04-14) via IRKernel 0.5

[willingc]

@Carreau @takluyver Thoughts? I'm seeing the same behavior as Chris (thanks for filing the issue) using the IJulia 0.4.5 kernel with similar OS config using Chrome or Firefox.

FWIW, there is some syntax highlighting with the same notebook in JLab alpha:

[takluyver]

I also see it, but I don't know what's causing it. There's no error in the JS console.

[Carreau]

It's the same that webpack that f**-up #1431 too, require just does not
work anymore, or at least not correctly, and there are basically 2
different CodeMirror library loaded on the page. So the mode is indeed
loaded correctly, but attached to the wrong copy of the module, so when the
cell highlighting changes, codemirror will just not find the mode, and give
up.

On Tue, May 10, 2016 at 9:34 AM, Thomas Kluyver notifications@github.com
wrote:

I also see it, but I don't know what's causing it. There's no error in the
JS console.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1439 (comment)

[Carreau]

And that unfortunately is #1047, that I just bisected, so the introduction of webpack did break all the kernels and many custom js and extensions.

Ping @ellisonbg , @fperez , @jdfreder as this is pretty important.

[ellisonbg]

Ouch, thanks for tracking this down. I am traveling more today. @jdfreder
is going to work on Friday for us and may be able to help us figure this
out...

On Tue, May 10, 2016 at 10:52 AM, Matthias Bussonnier <
notifications@github.com> wrote:

And that unfortunately is #1047
#1047, that I just bisected, so
the introduction of webpack did break all the kernels and many custom
js and extensions.

Ping @ellisonbg https://github.com/ellisonbg , @fperez
https://github.com/fperez , @jdfreder https://github.com/jdfreder as
this is pretty important.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1439 (comment)

Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgranger@calpoly.edu and ellisonbg@gmail.com

[willingc]

FWIW. When I started the notebook the output to the terminal had a message:

It looks like you're running the notebook from source.
    If you're working on the Javascript of the notebook, try running

        npm run build:watch

    in another terminal window to have the system incrementally
    watch and build the notebook's JavaScript for you, as you make changes.

Doing as instructed I opened another terminal window and ran this at the notebook source root directory and got these Babel errors:

[Carreau]

These are not errors, they are notes. Perfectly fine.

The issue is that webpack create a main.min.js, and an index.js . index.js
is meant to map the require calls to bundled modules, but main and index
end up being 2 different namespace, each with their own module versions.
On May 10, 2016 11:05, "Carol Willing" notifications@github.com wrote:

FWIW. When I started the notebook the output to the terminal had a
message:

It looks like you're running the notebook from source.
If you're working on the Javascript of the notebook, try running

    npm run build:watch

in another terminal window to have the system incrementally
watch and build the notebook's JavaScript for you, as you make changes.

Doing as instructed I opened another terminal window and ran this at the
notebook source root directory and got these Babel errors:

[image: screen shot 2016-05-10 at 9 50 50 am]
https://cloud.githubusercontent.com/assets/2680980/15155024/7edf403c-1695-11e6-855a-2807346ed2ed.png

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#1439 (comment)

[willingc]

@Carreau Thanks for the explanation. Too many JS details :P I appreciate the detailed explanation of the current issue 👍