Vidar Tonaas Fauske

I think I have a fix for this, but since the config resolution changes, I'll do it as a major version upgrade together with the upgrade to lab3 (I'll do...

(You can test it in [this branch](https://github.com/vidartf/nbdime/tree/config-update) until then if you want)

I included the first commit in #543. I'm not sure if the JSON one makes sense, as we already have structured JSON differ :) At the very least, I think...

The key to getting this fixed (and any other issues) would be to share some reproducible example. Where are those MBs for the notebook located? Are there any specific characteristics?...

@muxator The non-optimal brute force is a known issue (#3), but it is typically not a major issue for cells/source inputs, as these tend to be small. But if someone...

This might be an issue with how jupyterlab-git is using the nbdime REST API. Could you open up the developer tools in the browser, go to the network tab, use...

Thanks. I'd try to cross-post this to the jupyterlab-git repo as well (referencing this issue there and vice-versa). Note that nbdime assumes the path is given is relative to the...

Oh I'm sorry, I meant that I would recommend for you to do it. Sorry if the language was a little unclear.

Note that the actual diff processing of nbdime is running on the server. You can send it the files for processing using the (unfortunately undocumented) REST APIs: https://github.com/jupyter/nbdime/blob/master/nbdime/webapp/nb_server_extension.py Ideally the...

Also: How would you want to consume the diff? Do you want a rendered diff view, or do you want the diff as expressed by the JSON diff format?