-
Notifications
You must be signed in to change notification settings - Fork 293
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
[Feature Request] setting for interactive tab; number of cell text output lines #3677
Comments
My issue is probably related to this issue: Add support for running an entire file whether or not it has cells microsoft/vscode-python#3938 |
Looks like this is also now being discussed in microsoft/vscode-python#4009 for plots. Also need setting to apply to number of lines of text output. |
The following images illustrate the current (insiders build) behavior as the interactive tab width is expanded. The text in the test output is about 40 lines. When the interactive tab is narrow: horizontal scroll bar, no vertical scroll bar As it is expanded: no scroll bars As it is expanded to full width: vertical scroll bar reappears (upper and lower part of text shown) |
Can you include the python code you executed to cause the problem? I'm looking at this now and will likely add a setting. It won't be based on lines of text though, but rather pixels. |
Rich, Here it is. You can comment out the imported image code or sub in a new one. Pixels are fine. Just needs to allow a big number. The method arguments use string literals so markdown formatting below is affected. Thanks. ======= code starts ======== `# %% from IPython.core.interactiveshell import InteractiveShell from IPython.core.display import display,HTML import matplotlib.pyplot as plt gam = "\N{GREEK SMALL LETTER GAMMA}" def r__(ostr): def i__(ostr): def v__(ostr): def e__(ostr): def t__(ostr): def s__(ostr): #%%
i__(f'''| a caption image | size | |) #%%
i__(f'''| t | ic | The need to distinguish between {gam} the various i__(f'''| l | y |
v__(f'''values abcd | ref
e__(f'''equations abcd | ref
#%% section 0
i__(f'''This is a test {gam} = 2*{sig} of the system and this is a further test
of the system and another greek letter {Gam}
v__(f'''|some values | dasdfsa|
i__(f'''|text|
e__('''|some equations | abcd | ref
#%% section 0
i__(f'''This is a test {gam} = 2*{sig} of the system and this is a further test
v__(f'''|some values | dasdfsa|
#%% section 0
` |
@rholland this should be fixed in our latest release. You can set a 'maxOutputSize' (-1 if you want no restrictions). We use this value in the css for the output portion of a cell. |
Environment data
Expected behaviour
First - thanks a lot for the default behavior of hiding input in the interactive window. It is very nice.
In previous versions of the extension the output frame for each cell appeared to be as long as necessary. This is preferred behavior in my view. In the insider build the max length is about 20 lines.
Actual behavior
In 2019-alpha the maximum output frame depth appears to be about 20 lines. Anything longer generates a scroll bar to view the rest. I strongly prefer the previous behavior of apparently unlimited frame depth. If others prefer the vertical scrolled behavior then could you please make a user controlled setting for the maximum lines per frame with a setting for no limit.
If for some reason you need to have a built-in fixed number at this point, please set it to a larger number - say 50 lines. 20 is too small and leads to fussy, non-intuitive behavior.
The first problem is that cell output needs to be scrolled, which takes a lot of time and motion.
The second problem is that scrolled windows are nested (the output frame within the interactive pane) so scrolling with a mouse gives awkward and unpredictable effects when looking at all the output.
Because of the scroll in a scroll, the whole output cannot be easily reviewed from the keyboard - the cursor gets stuck in an output frame.
All of this leads to awkward behavior when reviewing cell output longer than a few lines and the output as a whole. If this behavior is just part of the alpha development and the behavior at release will not include individual scrolled cell outputs, rather the behavior will be the same as the past with unlimited cell output lengths, then disregard the above.
Thanks again for the great tool.
The text was updated successfully, but these errors were encountered: