I try to set my cursor at very last column of the line, but when clicked, it sets my cursor at a wrong point in the middle of the line. I feel this pain even when I paste something into my codebase, it pastes into wrong selection. In another words, it don’t allow me to select correctly.
Hey, thanks for the report and the screenshot. In the image, the mouse I-beam is on the right, but the actual caret lands after ) in the middle of the line. That’s a horizontal offset. This looks like a known issue with font character width measurement in the editor font metrics. No data is lost, and it’s usually quick to fix.
Glad a restart fixed it. Since you’re on a single laptop screen with no second monitor, it’s most likely the font metrics were measured before the font fully loaded. That’s usually a one-off glitch, not a persistent state, so there’s nothing to worry about right now.
For next time, if the cursor starts missing again, you don’t need to reinstall anything. Just use Ctrl+Shift+P then Developer: Reload Window, or do the same trick of toggling editor.fontFamily back and forth. That forces a re-measurement, and one of these steps is usually enough.
JetBrains Mono and Fira Code aren’t the cause, so no need to change them. Keep whatever feels best. If the bug comes back regularly, post here and we’ll take a deeper look.
Hi @deanrie, I have opened my Cursor today and I got the same issue again. I don’t want to restart or toggling editor.fontFamily each time I open it. Could you please make an stable solution?
It’s frustrating that this is back. This is a known issue with how the editor measures font character widths. The metrics are captured once when the window starts, and if font rendering hasn’t warmed up yet at that moment, clicks can map to the wrong column. There’s no permanent fix yet, and I can’t give a reliable ETA. I reported it internally so we can track it.
What can make it more stable: try setting editor.fontFamily to a single font instead of a list like JetBrains Mono, Fira Code. A fallback list can sometimes trigger a race during metric initialization, and using one font avoids that.
If it happens again, restarting every time isn’t great. Ctrl+Shift+P then Developer: Reload Window is usually faster than a full restart and it also forces the editor to re-measure.
Let me know if using one font helps. If it still comes back after that, we can dig deeper.
Got it, this is easier than it looks. You can open the Command Palette without Ctrl+Shift+P.
Press F1. This is the second default shortcut for Command Palette.
Or use the menu: View → Command Palette, then type Developer: Reload Window.
If you want to get Ctrl+Shift+P back, you can remap the Snipping Tool shortcut in Windows settings, or set your own shortcut in Cursor: File → Preferences → Keyboard Shortcuts, find workbench.action.showCommands, and bind a combo you like.
