-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
IDLE: properly handle '(' and ')' within calls #84691
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
Comments
The yellow frame blinks as shown in mp4. It's annoying and isn't good to the eyes. |
OMG, request too large. I can't upload mp4 /(ㄒoㄒ)/~~ |
|
Each '(' and ')' in an argument string such as in f('()(()()((((())))))))))))))') causes a blink. Ditto with a comment withing the call. A related bug is that any unquoted '(', as when one enters f((a+b)*c), dismisses the tip. Proposed partial solution: before displaying a tip, record the opening index (before the opening '('). When there is an opening index, and '(' is keyed, ignore it; no parsing. When the tip is closed (properly), removed the open index. I believe paren matching would work properly. The cause of blinks for ')' in strings and comments would need to be found and remedied. |
I agree that this should be improved. Terry, on the technical side, IDLE already has good tools for parsing the current code line/block and figuring out whether the cursor is in a string, a comment or parentheses. This should be possible to solve in a robust way without writing any new parsing logic. I'll try to take a look at this soon. |
You can try to reduce the video's resolution and/or framerate in order to reduce its size. Usually screen captures are taken at high resolution and framerates by default, making the resulting video files very large, which is a sensible default but not great for attaching to bug reports. |
Confirmed on latest master on macOS 10.15.5 with Tcl/Tk 8.6.10. |
See PR #65109 with a fix. |
wyz, thank you for the report. It should be fixed now. |
Thanks! :D |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: