We should include syntax highlighting for the exception traceback while copying to a rich text environment (e.g. outlook).

Hi!

is there any plans to update the version in NPM repository for this package? The latest version there is quite old: https://www.npmjs.com/package/jupyterlab-skip-traceback

Thank you!

Let me know if there is anything I can help with.

Most JupyterLab v3/v4 extensions have support for both the JupyterLab notebook interface as well as the Notebook v7 interface. (e.g. the NB v7 extensions page mentions this and also links to jupyterlab-skip-traceback in the page describing the transitioning from Classic Notebook to Notebook 7.)

However, it seems this extension does not support Notebook v7. For instance, here's the same notebook opened in the Lab interface (shows the collapse button) and then in the Notebook v7 interface (no collapse button):

Is it possible to extend this so that it works for Notebook v7 as well? Thank you for building this functionality!

I use Neon Theme. I would like to use skip-traceback to experience short error messages too. But the different theme used in the add-on looks weird and uncomfortable to the eyes.

Default error view on Neon Theme:

Skip-traceback (collapsed):

• I dislike the red color on the error background.
• I wish the syntax coloring remained the same as the last line of traceback, i.e. something like this:

Skip-traceback (expanded):

• The red color on the error background is unwelcome to the eyes.

VS Code takes the top spot for development environments (see link to the 2023 Stack Overflow survey below). I love your plugin for JupyterLab and wanted to know if you would consider making it available for use with Jupyter Notebooks in VS Code as well.

https://survey.stackoverflow.co/2023/#section-most-popular-technologies-integrated-development-environment

Since update to JupyterLab 4 the GitHub actions workflow is configured to run on main:

but the default branch is still named master.

Would it be worth renaming the default branch to main or updating the workflow file?

Hi, it seems that your extension is not compatible with version 3 of Jupyterlab.
Thx for your help.

The upcoming JupyterLab 4.1 will support linking to paths. jupyterlab-skip-traceback replaces application/vnd.jupyter.error renderer it disables linking. This is because JupyterLab 4.1 defines a new renderError function which enables opening files from tracebacks but jupyterlab-skip-traceback uses the old renderText:

This will need to be swapped in a future version to support linking to paths.

One very useful use case for the skip traceback extension is in educational settings, where verbose error traces are hidden from students unless they really want to see them.

Having to provide instructions to novice uses how to got into setting to effectively make use of the functionality of the extension is a painful overhead, eg when writing explanatory text to get students started quickly.

If an educator is in control of a student environment, eg providing a predefined containerised environment, then default settings can be modified via a configuration file, but if students are using a "found" environment into which they have installed the extension themselves, they will be presented with the uncollapsed errors by default.

Is there a particularly strong reason for not enabling the collapsed state by default, escpecially give the extension is called skip-traceback not optionally-skip-traceback?