You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 21, 2022. It is now read-only.
When I hit the "/" key to search with the vim plugin active, I get the following error in a dialog box:
Not an editor command ":ltexec vim.find"
When I search for this I find a keybinding in the vim plugin's source. Suspecting there was an api change, I added the following to my keybindings:
:editor { ...
"/" [:vim.find]}
and after saving this it seems to work. However, I can't get rid of the error messages about :ltexec find.next and :ltexec find.prev by adding similar key bindings for n and shift-n.
The text was updated successfully, but these errors were encountered:
When I hit the "/" key to search with the vim plugin active, I get the following error in a dialog box:
When I search for this I find a keybinding in the vim plugin's source. Suspecting there was an api change, I added the following to my keybindings:
and after saving this it seems to work. However, I can't get rid of the error messages about
:ltexec find.next
and:ltexec find.prev
by adding similar key bindings forn
andshift-n
.The text was updated successfully, but these errors were encountered: