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
send to console does not work #16272
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
I run into very similar issue. I was able to run a single selected line by putting the cursor at the beginning of the line. After upgrading to 4.2.0, The shortcut "Shift+Enter" does not work anymore, no matter how I place the cursor. But if I use click the "Run selected code" in the "run" menu, the line successfully runs on the console. I guess it is an issue related to keyboard shortcut. |
Description
A common work flow I have is to open a
.py
file, then create a console for it. I'll then interactively work, running line by line by sending to console with shift+enter. I am finding that in certain (common) situations some lines won't send to console.I have found two work arounds:
Reproduce
.py
fileSending the first line will work. Update to:
Now the first line will not send.
Update to:
Now the first line will send again.
Update to:
This will send, but it positions you between the first and second character of line 3.
(This assumes you're placing the cursor at the right-end of the line in these tests).
It seems if the cursor position is greater than the length of subsequent lines (combined?) it will send, but it jumps to a line-length dependent position (not always to the end of the line).
Expected behavior
The sending of code should not be line-length dependent. It should send and jump your cursor to the next line of code (and be positioned at the same relative position (beginning or end of line).
Context
I can provide the troubleshoot and command line output, if needed, but the "out of range" error seen in the browser output seems to me that it might be sufficient info.
Troubleshoot Output
Command Line Output
Browser Output
The text was updated successfully, but these errors were encountered: