Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi! It's an optional solution to use a keyboard scancode.
Based on the comment: #165 (comment)
And on: #10228
Introduced the new feature
scancode
to enable the following logic:KeyEvent
and pass it back.It isn't required to change user keymap configurations.
cargo install --features scancode --locked --path helix-term
Config
And it works well on my setup (linux/x11 and qwerty keyboard).
I tried to implement it in a separate module and simplify the API as an optional helix feature.
Such an approach as the
compilation flag
for "desktop" Helix users is the right way?