-
Notifications
You must be signed in to change notification settings - Fork 299
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
enable "Toggle Cell Output Scrolling" like in native jupyter notebook #12496
Comments
tracking this in #4406 You can enable the experimental feature by adding |
@amunger when I add that setting it is grayed out signaling to me that it is not an option that exists. How do I enable it? EDIT: it also does not change the notebook cell output in any way |
it's expected to be grayed out since it's still experimental and undocumented. You'll need to reload vs code after adding the setting and then it will only affect cells where the content is long enough to need scrolling (instead of showing the |
ok great it is working now. Thank you for explaining to me how to work it |
Is it possible to use a keyboard shortcut to focus on the scrollable output area and smooth scroll the output using a keayboard only? |
@miumer - please create a new issue for that feature request so it can be tracked independently |
This confused me, so I'm including a comment here: The feature setting only applies a scroll bar to But it removes the line length limit for both output types!! |
I think this is identical to #12122 but that one is closed and this feature does not exist to my knowledge.
in Jupyter Notebook, you can toggle cell output scrolling so that large outputs still print, but you don't have to scroll for days to get to the next cell. Instead the output window has a scroll bar and you can scroll only the output. This would be a very nice feature to have since the current option is to have long outputs appear in a new editor window and this works for normal outputs, but is horrible for errors which get truncated and then you can't really read them in the new editor.
The text was updated successfully, but these errors were encountered: