Skip to content
This repository has been archived by the owner on Mar 29, 2024. It is now read-only.

conflict with emacs key bindings after enabling fuzzy file search #1

Open
BigRedT opened this issue Aug 25, 2017 · 4 comments
Open

Comments

@BigRedT
Copy link

BigRedT commented Aug 25, 2017

When I enable fuzzy file search from command palette, vscode no longer recognizes my arrow keys or other emacs key bindings like C-a, C-e etc. I can still type text in the editors though. But if I disable the fuzzy search extension, the key bindings work as expected.

I am using emacs key bindings available in Emacs Friendly Keymap Extension for VSCode. I am on OSX platform.

Would really appreciate a fix for this! The fuzzy search seems to be significantly faster than the usual search with Cmd + P when accessing directories mounted with sshfs and I would love to keep using it.

@gayanhewa
Copy link
Owner

gayanhewa commented Sep 8, 2017

@BigRedT can you share the Emacs keybinding extension and version that you have enabled. Ideally there shouldn't be a conflict. Unless you have modified the default keybindings then you will have to remap the keys to get it to work.

@BigRedT
Copy link
Author

BigRedT commented Sep 8, 2017

@gayanhewa I am using v0.8.0 of the following extension:
https://marketplace.visualstudio.com/items?itemName=lfs.vscode-emacs-friendly

I did not modify the keybindings besides installing this extension.

@gayanhewa
Copy link
Owner

Seem to be working alright for me:

fuzzy-with-emacs

@BigRedT
Copy link
Author

BigRedT commented Sep 8, 2017

arrow keys work fine in the command palette but not in the editor. Try the following sequence of steps:
open a file with some content in the editor window > enable fuzzy file search > move cursor to the editor window > try using arrow keys to move around

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants