This repository was archived by the owner on May 12, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 426
Custom vim mappings #464
Copy link
Copy link
Open
Labels
feature request 🌟Issue is a new feature request.Issue is a new feature request.funded on issuehunt 💵Issue has received funding that will be rewarded to the contributor solving this issue.Issue has received funding that will be rewarded to the contributor solving this issue.help wanted 🆘Pull request/issue requires extra help from the community. Check these out if you're new!Pull request/issue requires extra help from the community. Check these out if you're new!needs specs 📐issues requiring specsissues requiring specs
Metadata
Metadata
Assignees
Labels
feature request 🌟Issue is a new feature request.Issue is a new feature request.funded on issuehunt 💵Issue has received funding that will be rewarded to the contributor solving this issue.Issue has received funding that will be rewarded to the contributor solving this issue.help wanted 🆘Pull request/issue requires extra help from the community. Check these out if you're new!Pull request/issue requires extra help from the community. Check these out if you're new!needs specs 📐issues requiring specsissues requiring specs
Type
Fields
Give feedbackNo fields configured for issues without a type.
Current behavior
No custom vim keyboard mappings in the UI. A trick proposed on legacy BoostNote's wiki page won't work either.

Expected behavior
Some way of customizing vim mappings will be possible.
Steps to reproduce
Same as in linked wiki article.
Environment
Desktop/Web
Is it a bug / missing feature and in such case is there any ETA on making this work?
IssueHunt Summary
Backers (Total: $20.00)
Submitted pull Requests
Become a backer now!
Or submit a pull request to get the deposits!
Tips