Vidar Tonaas Fauske

Hi! I think this sounds like a good idea, but it would maybe be cleaner to make a separate handler and entry point instead of adding a flag, i.e.: -...

Hello! First of all, which version of nbdime are you using? 😃 Regarding the `--ip xxx.xxx.xxx.xxx` argument, that would be used in the command that starts nbdime. How are you...

The output you are seeing is definitely coming from nbdime. Can you be more specific in what differences you are thinking of? The execution count flags can be ignored with...

Looking at this again, from your original post, it seems like the big base64 data is *inside an HTML output which contains a PNG*. Currently, we can truncate the PNG...

Hmm.. Then I would say that this works as expected. There is an outstanding issue of whether to try to find base64 strings in html outputs. Anyone who wants to...

An alternative logic could also be: Truncate any output data longer than X lines/characters. This could possibly add a `-v/--verbose` flag to expand these (would also expand base64?).

The two nbdiff outputs you list are different scenarios: - In the first case, the image data is exactly the same, but the value put into the plaintext field by...

Cross referencing with #530, as that would be similar. I guess options could be: - Only show "outputs changed" always. - Show "outputs changed" only for outputs over a certain...

If anyone has a set of notebooks that reproduce this issue, that would really help ensure this to be resolved (the logic is complex enough that a trace alone is...

Ah, I think this is a case of poorly written documentation on my part. The global config object is for all commands, *but only for options that are supported by...