Vim Mode: "go to definition" will switch to visual mode

[derekuang]

Summary

As title, after update zed to 0.213.3(Windows platform), the action "go to definition" by typing "g d" in vim mode will switch to visual mode.

Description

DESCRIPTION_HERE

Steps to reproduce:

1. enable vim mode
2. find a function call
3. enter "g d" to go to definition
4. done

Expected Behavior: keep in normal mode
Actual Behavior: switch to visual mode

Zed Version and System Specs

Zed: v0.212.3 (Zed)
OS: Windows 10.0.19044
Memory: 31.8 GiB
Architecture: x86_64
GPU: NVIDIA GeForce GTX 1050 Ti || NVIDIA Corporation || 536.23 r536_08

If applicable, attach your Zed.log file to this issue.

Zed.log

[aaron-18-112]

+1

[Edgarfp]

Yes, I can confirm this is happening in Zed's Linux version also.

[dinocosta]

Thank you for reporting! I was already taking a look at #42705 but, while trying to reproduce this issue in Zed Preview (0.213.1) it seems to be hit or miss, it doesn't happen every time ▼

CleanShot.2025-11-17.at.12.35.28.mp4

@derekuang @aaron-18-112 @Edgarfp Does it consistently reproduce for any of you in that same version of Zed? I saw it happen once or twice but not always, not sure what's going on but will try to find more information.

P.S.: Seems like it always happens if the file where the definition is located is already open, otherwise it does not.

[aaron-18-112]

Thank you for reporting! I was already taking a look at #42705 but, while trying to reproduce this issue in Zed Preview (0.213.1) it seems to be hit or miss, it doesn't happen every time ▼

CleanShot.2025-11-17.at.12.35.28.mp4

@derekuang @aaron-18-112 @Edgarfp Does it consistently reproduce for any of you in that same version of Zed? I saw it happen once or twice but not always, not sure what's going on but will try to find more information.

Seems to be intermittent for me as well but definitely occuring more often than not

[dinocosta]

@aaron-18-112 Thank you for the quick reply! Are you able to confirm the behavior I'm seeing where this always happens if the file where the definition is located is already open? It seem that, if the definition's file is not open, it does not happen.

CleanShot.2025-11-17.at.12.42.16.mp4

[aaron-18-112]

@aaron-18-112 Thank you for the quick reply! Are you able to confirm the behavior I'm seeing where this always happens if the file where the definition is located is already open? It seem that, if the definition's file is not open, it does not happen.

CleanShot.2025-11-17.at.12.42.16.mp4

I'm seeing it when the file is closed as well sometimes when going from the global search into files it is happening