Hey, this sounds like the same issue other non‑English keyboard users have reported with the Cursor 2.0 upgrade. Here’s a particular workaround that helped, so that may be worth trying.
Hey, this sounds like the same issue other non‑English keyboard users have reported with the Cursor 2.0 upgrade. Here’s a particular workaround that helped, so that may be worth trying.