-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Key bindings in custom commands are all mapped to lower cases #3470
Comments
hi, I'll like to give this one a try. Can someone assign me? |
@dsolerh feel free to take it, do note that I'm not sure if this is just a bug that we map everything as lowercase, or if we can't actually detect |
yes, I think the clear way to implement it will be using |
Hi, I can't find a way to capture an key event when I press ctr+shift+, I. think that the tcell package does not support this: |
@stefanhaller you've been elbow-deep in the tcell, you could probably answer this off the cuff. |
I'm not an expert here either, but my suspicion is that it's just not possible unless tcell implements gdamore/tcell#671. |
Describe the bug
In my config.yaml I've set two custom commands to push and pull to specific remotes and branches. This part of the config is shown as below
The key bindings for these two commands are
<c-p>
and<c-P>
. But in actuality they are all mapped to<c-p>
in lazygit, see the screenshot below:To Reproduce
As described in the bug description
Expected behavior
I'm not sure whether the custom command keybindings support the capital letter or am I just missing some config settings to setup a keybinding with capital letter.
Version info:
lazygit version:
commit=3675570a391b1a49ddd198b4c7e71e17701d4404, build date=2024-03-23T09:09:11Z, build source=binaryRelease, version=0.41.0, os=windows, arch=amd64, git version=2.43.0.windows.1
git version:
git version 2.43.0.windows.1
Note: please try updating to the latest version or manually building the latest
master
to see if the issue still occurs.The text was updated successfully, but these errors were encountered: