Skip to content
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

[Feature Request] Ability to key blind configs #13

Open
Maverun opened this issue Apr 16, 2022 · 2 comments
Open

[Feature Request] Ability to key blind configs #13

Maverun opened this issue Apr 16, 2022 · 2 comments

Comments

@Maverun
Copy link

Maverun commented Apr 16, 2022

I believe having configs for key blind would be created
I at least want to have
ctrl+a, ctrl+e, ctrl+w during insert mode to be support
(ctrl+a allows to go to the start of the line, ctrl+e allows move cursor to end of the line,
ctrl+w is the same as db in vim, delete word backward)

I use those often during terminal/weechat/terminal
And I think those would be useful

Maybe we can set key blinding for each field? (one for main menu, input etc)
I think it could get complex and maybe stick with simple overall blinding for all?

@PlankCipher
Copy link
Owner

This will be added in the next release which will introduce a config file. I think it will be possible to bind keys in different areas, e.g. main menu screen, columns, cards, inputs, etc. But I think keys will be bound to components generally, for example you will be able to customize the input component bindings generally, but won't be able to separate the input in main menu from that in the board screen for example. I think separating them would be an overkill and not really necessary. Sorry for the late response.

@PlankCipher
Copy link
Owner

Reopening this until implemented/fixed.

@PlankCipher PlankCipher reopened this Jan 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants