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
In the workflow where one launches the search-editor (to find files with content matching a certain string), the textbox (input box) doesn't respect Emacs key-bindings. Eg. Ctrl+f won't move the cursor forward etc.
Unsure if I have used the right name to describe the problem, here is the screenshot of the component that I am referring to. In this case the search term is dataplane.
Search is a fairly common operation and it breaks the flow because one need to switch to arrow-keys to modify the search-term.
I think this would be a valuable feature to have. I am also happy to help implement it (although I have very little experience with VSCode plugin development and have never looked at emacs-mcx source tree, so someone will have to point me in the right direction).
The text was updated successfully, but these errors were encountered:
It is also entirely possible that I am missing something (or it may be possible to bind a shortcut specifically for this usecase outside of emacs-mcx). Would really appreciate any inputs that help me do that.
In the workflow where one launches the search-editor (to find files with content matching a certain string), the textbox (input box) doesn't respect Emacs key-bindings. Eg. Ctrl+f won't move the cursor forward etc.
Unsure if I have used the right name to describe the problem, here is the screenshot of the component that I am referring to. In this case the search term is
dataplane
.Search is a fairly common operation and it breaks the flow because one need to switch to arrow-keys to modify the search-term.
I think this would be a valuable feature to have. I am also happy to help implement it (although I have very little experience with VSCode plugin development and have never looked at emacs-mcx source tree, so someone will have to point me in the right direction).
The text was updated successfully, but these errors were encountered: