Unable to paste, delete word, etc. in UI inputs #185

darth_mall commented 2026年03月31日 17:21:46 +02:00

I'm unable to use shortcuts like Ctrl-v or Ctrl-Backspace in the user interface inputs, such as the command palette or the dialog for installing an extension from a URL.

I have Vim mode turned on, and am using version 1.2.1.

I'm unable to use shortcuts like <kbd>Ctrl</kbd>-<kbd>v</kbd> or <kbd>Ctrl</kbd>-<kbd>Backspace</kbd> in the user interface inputs, such as the command palette or the dialog for installing an extension from a URL. I have Vim mode turned on, and am using version 1.2.1.

aylamz commented 2026年03月31日 17:33:54 +02:00

this could be due to base keymap being emacs by default maybe. in settings under "keymap", try changing "base keymap" to vscode for example

this could be due to base keymap being emacs by default maybe. in settings under "keymap", try changing "base keymap" to vscode for example

darth_mall commented 2026年03月31日 23:45:33 +02:00

Yeah, it looks like that's the problem. I use Vim mode, so I have set the base keymap set to "Minimal." The problem is that this prevents me from, for example, pasting a URL for an extension into the remote installation dialog.

I wonder if the minimal keymap could be updated so that outside of the text buffers keyboard shortcuts continue to work like they do in other GUIs. Not sure if that would be a new issue, or if we just continue the discussion here.

Thanks for the help.

Yeah, it looks like that's the problem. I use Vim mode, so I have set the base keymap set to "Minimal." The problem is that this prevents me from, for example, pasting a URL for an extension into the remote installation dialog. I wonder if the minimal keymap could be updated so that outside of the text buffers keyboard shortcuts continue to work like they do in other GUIs. Not sure if that would be a new issue, or if we just continue the discussion here. Thanks for the help.

tjk commented 2026年04月01日 00:16:00 +02:00

I wonder if the minimal keymap could be updated so that outside of the text buffers keyboard shortcuts continue to work like they do in other GUIs. Not sure if that would be a new issue, or if we just continue the discussion here.

I think arguments could be made both ways:

1. the hotkeys from other editors could be added to places like this, where you're less likely to assume that vim keys would work
2. more vim keys could be added, since Gram has surprisingly good vim-key support; normal mode works in these types of dialogs too, so you could 'p' for paste

Certainly (1) is easier, and I'm not sure I'm enough of a purist to do the work for (2). Before someone jumps on (1), though, I'd suggest we clarify the general idea of which bindings should be in minimal, which should be in vim keys, and which shouldn't be in either. My thoughts:

• In vim keys: bindings that come from vim, are common in vim setups, or use vim-like bindings for new Gram functionality
• In Minimal: bindings that aren't from vim but are basically necessary to operate a GUI, and don't conflict with vim
• In neither: well, the point of the minimal base keymap + vim keys is to allow users to have a vim-like interface without needing to unbind / replace keys from other editors, so at a minimum, if a key is used for something else in vim, I'd suggest not adding it

> I wonder if the minimal keymap could be updated so that outside of the text buffers keyboard shortcuts continue to work like they do in other GUIs. Not sure if that would be a new issue, or if we just continue the discussion here. I think arguments could be made both ways: 1. the hotkeys from other editors could be added to places like this, where you're less likely to assume that vim keys would work 2. more vim keys could be added, since Gram has surprisingly good vim-key support; normal mode works in these types of dialogs too, so you could 'p' for paste Certainly (1) is easier, and I'm not sure I'm enough of a purist to do the work for (2). Before someone jumps on (1), though, I'd suggest we clarify the general idea of which bindings should be in minimal, which should be in vim keys, and which shouldn't be in either. My thoughts: * In vim keys: bindings that come from vim, are common in vim setups, or use vim-like bindings for new Gram functionality * In Minimal: bindings that aren't from vim but are basically necessary to operate a GUI, and don't conflict with vim * In neither: well, the point of the minimal base keymap + vim keys is to allow users to have a vim-like interface without needing to unbind / replace keys from other editors, so at a minimum, if a key is used for something else in vim, I'd suggest not adding it

krig commented 2026年05月14日 23:16:19 +02:00

Hello,

I've decided to go through and close issues that I don't intend to fix. If it's a feature request for something that I haven't planned to do, then I would encourage you as the reader to fix it yourself! It's open source, I'm guessing most people who are using a code editor are coders, and it's good for you to learn new things. I've come to realize that I can't fix WGPU issues on a particular piece of hardware for example. Whoever has that problem will have to solve it so they can verify that the fix actually works.

If it's a packaging thing, like providing packages for a particular OS, Linux distro or architecture, then all I can say is that I have tried and there just isn't enough time in my life to support everything people want. What I have done is hook up this repo to a Github mirror with actions enabled: https://github.com/GramEditor/gram. My suggestion to anyone who needs or wants a particular build is to make a PR that adds build support that way.

Hello, I've decided to go through and close issues that I don't intend to fix. If it's a feature request for something that I haven't planned to do, then I would encourage you as the reader to fix it yourself! It's open source, I'm guessing most people who are using a code editor are coders, and it's good for you to learn new things. I've come to realize that I can't fix WGPU issues on a particular piece of hardware for example. Whoever has that problem will have to solve it so they can verify that the fix actually works. If it's a packaging thing, like providing packages for a particular OS, Linux distro or architecture, then all I can say is that I have tried and there just isn't enough time in my life to support everything people want. What I _have_ done is hook up this repo to a Github mirror with actions enabled: https://github.com/GramEditor/gram. My suggestion to anyone who needs or wants a particular build is to make a PR that adds build support that way.