-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
keymaps: Fix how single line editor handles new lines in BufferSearch #19316
keymaps: Fix how single line editor handles new lines in BufferSearch #19316
Conversation
Hi @narqo, These changes are not correct: zed/assets/keymaps/default-macos.json Lines 234 to 240 in 709581b
|
709581b
to
5410d14
Compare
@notpeter, you're right, my bad. I missed that part that I'm using JetBrains preset, where the |
I was able to actually reproduce this with the default vscode keymap + vim mode and so I think the underlying issue might be one with Vim mode contexts. That is, zed/assets/keymaps/default-macos.json Lines 222 to 227 in 9d61cd5
It's probably worth filing an issue as changing the keymap is not likely the correct solution. |
I don't use Vim mode, but I use the |
Thanks! |
This PR updates the JetBrains keymaps preset to handle the
shift-enter
combination as theSelectPrevMatch
action.That is, it seems that, with the current defaults, pressing the Shift+Enter inside the search editor (
single_line
mode Editor inside theBufferSearchBar
) triggers the "Editor::newline". With the updated defaults, it works as I expect it.Also, the PR adds thealt-enter
in the context of the editor inside theBufferSearchBar
to trigger the newline. This matches with how it works in other editors on macOS, e.g. in Xcode.Release Notes: