-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Cursor rendering issue in Python Interpreter started with latest VS code version, 1.86.0 #22866
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
Hello, @julianghadially thank you for filing this issue. So are you saying you are not able to go back to previous line of 'multi-line' command written in REPL? If that's the case, I'm not sure if I can repro that (See attached) As far as " I need a way to send multi-line blocks to the terminal line-by-line (e.g., using shift-enter). " Screen.Recording.2024-02-09.at.2.51.17.PM.mov |
Looking at your video, you've replicated the exact situation, but with my environment, the rendered cursor stops when it reaches the leftmost part of the line, but the true cursor continues. So from then on the edit location displayed to me is not actually the true edit location. Is there any other information you need to resolve this? |
I am experiencing something similar. However, it happens every time I launch a terminal with "Python: Run Selection/Line in Python Terminal". The cursor displays 47 characters ahead of the position I'm editing. It's very disruptive. Solutions I've tried:
|
I just did some testing. This issue appears to start with version 2024.0.0 of the extension. That's the first version where it happens to me. It does not occur when I'm using version 2023.22.1. |
This should be fixed now. Its coming from cpythn3.13 python/cpython#126131 |
@julianghadially are you still suffering from this on the latest insider version of VS Code? |
Also wondering if its people are able to repro outside of Python REPL in terminal. Do typing other long commands in VS Code terminal repro the problem? |
Yes it's fixed now. Thanks. |
Type: Bug
Behaviour
Expected vs. Actual
I'm experiencing a very disruptive cursor rendering issue in python interpreter, when I updated to the latest vs code 1.86.0. The cursor in the python interpreter gets stuck on code lines that span multiple lines: When tracking to the left, the rendering gets stuck and edits at a different location than displayed. Vs Expected: you should be able to scroll to the left and have the cursor not get stuck.
I reverted VS Code and python extension to older versions, and the issue was still present.
System information: VS code version 1.86.0 and 1.85.2 (tried fixing across multiple versions)
Python version: 2024.0.0 and 2025.25.10292213.vsix
Steps to reproduce:
After this error, if you press the down arrow, the cursor rendering is way off in random places, and it gets really wacky (e.g., cursors in the middle of the screen, etc.

The problem does not occur when I start python from the terminal.
Ultimately, I need a way to send multi-line blocks to the terminal line-by-line (e.g., using shift-enter). This is a critical efficiency need that dictates which ide I use. There weren't any problems until the most recent updates to 1.86.0
Note: I tried many options like disabling GPU acceleartion, hardware acceleration, and anything i could find from searching for this issue.
Diagnostic data
python.languageServer
setting: DefaultOutput for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)User Settings
Extension version: 2023.25.10292213
VS Code version: Code 1.85.2 (8b3775030ed1a69b13e4f4c628c612102e30a681, 2024-01-18T06:40:32.531Z)
OS version: Darwin x64 21.6.0
Modes:
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: