User defined keyboard shortcuts #219
Labels
No Label
blocked
bug
build
documentation
duplicate
enhancement
finger
gemini
gopher
help wanted
http
in progress
invalid
local
needs-info
non-code
non-functional
non-urgent
question
release
rendering
suggestion
telnet
terminal
urgent
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sloum/bombadillo#219
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is there a way to change the default keyboard shortcuts in bombadillo?
Like using a key other than
u
to scroll a page up.Not on the fly. It is really easy to modify that particular section of the code and recompile though. Go here to see the function in question. It is just a big switch statement, so you'll see something like (in the case of your example):
Which you could change to, lets say... "n" for some reason:
You just want to make sure it doesnt take up a key that is being used for something else. If it is, you will want to change that other key as well.
Then you would just recompile by running
make
from within the repo directory. If you need any help doing this let me know and I'd be happy to help. I could, for a future version, likely create a var list in its own file for this purpose and then reference those variables. For now though, editingclient.go
around the line linked above is the best way to go about it. Feel free to e-mail me on rawtext club if you need or want help. I can likely even produce a binary for you if you want to just email the keys you want changed (if you dont feel comfortable doing it yourself).Thanks!
I edited client.go and made it to this.
Compilation was easy enough thanks to the Makefile.
I was wondering why page scrolling was kept at 75% and not 100%.
Now I see why.
It scrolls too much.
But couldn't figure out why. 100% seems to mean more than 100% sometimes?