-
Notifications
You must be signed in to change notification settings - Fork 29k
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
IPython ?/?? output doesn't render nicely in the text editor #200263
Comments
This applies to other colored outputs as well, not limited to |
I assume so but that should be confirmed. |
Similar problem with exception outputs can be found here |
Still having this problem, any solutions. The full output is completely unreadable. Thank you! |
being able to view outputs in a scrollable region should help with this (toggle with It is surprisingly hard to fix the 'open in separate file link', but we should be able to strip out these extra characters in the |
Applies To
What happened?
IPython provides
?
and??
to get a quick access to the help and source code of an object. When the output of this magic command is too long VSCode suggests opening it in a text editor (Output exceeds the size limit. Open the full output data in a text editor
). However, I believe that IPython expects the output to be displayed in a terminal and as such colorizes it. This doesn't render nicely at all in the text editor.Execute the following in a Notebook cell:
Follow the suggestion and open the text editor, you'll see:
(Originally reported in holoviz/hvplot#984)
VS Code Version
Version: 1.73.1 (Universal) Commit: 6261075 Date: 2022-11-09T02:08:38.961Z Electron: 19.0.17 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Darwin x64 21.4.0 Sandboxed: No
Jupyter Extension Version
v2022.9.1303220346
Jupyter logs
No response
Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
None
The text was updated successfully, but these errors were encountered: