You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Note: I'm posting this as it indicates a bug not because I have an issue with it, specifically. I am no longer using the shifted mapping, but the fact that shifted mapping fails so inconsistently is, ofc, notable]
Remap: (hjkl~~>jkl; && ; ~~>h)
A config.toml with notes and images of same with failed remappings highlighted is attached.
The nature of the failures is not consistent.
Sometimes the hjkl behavior is retained.
Sometimes no effect is produced.
Sometimes it's for one direction and not another where as sometimes its for all directions.
And 'Visual' mode no longer highlights with direct arrow movement keys.
Example failing config.toml file (Note: remove the .txt at the end -- had to postpend that to get github to load it & and of course remove the description pre- config.toml) failing_key_remapping-config.toml.txt
Reproduction Steps
Highlighted and annottated remapping images attached.
The config.toml file also attached so one can just switch that in and drive it themself.
Helix log
~/.cache/helix/helix.log
please provide a copy of `~/.cache/helix/helix.log` here if possible, you may need to redact some of the lines
For most of these, this is a limitation of TOML. Each successive table is overwriting the last instead of being merged.
You have to use a single table for all sub-keys:
[keys.normal]
z = { k = "scroll_down", l = "scroll_up" }
Or use:
[keys.normal.z]
k = "scroll_down"l = "scroll_up"
For the "doesn't work (doesn't select text, but does move)" ones, this is expected behavior. Use extend_* commands (extend_char_left/extend_line_down/extend_line_up/extend_char_right) instead of move_* to keep the selection as you move.
Made those changes and everything works. So this was a TOML-syntax (+ one bit of Helix-semantics) issue.
Thanks.
Very unfortunate (read: ugly) that TOML inline tables can't have new lines -- forcing single huge lines instead of readable blocks. But that's a TOML limitation apparently.
Changed, working config for reference for others that might run into similar problems:
Summary
[Note: I'm posting this as it indicates a bug not because I have an issue with it, specifically. I am no longer using the shifted mapping, but the fact that shifted mapping fails so inconsistently is, ofc, notable]
Remap: (
hjkl
~~>jkl;
&&;
~~>h
)A config.toml with notes and images of same with failed remappings highlighted is attached.
The nature of the failures is not consistent.
Sometimes the hjkl behavior is retained.
Sometimes no effect is produced.
Sometimes it's for one direction and not another where as sometimes its for all directions.
And 'Visual' mode no longer highlights with direct arrow movement keys.
Example failing config.toml file (Note: remove the
.txt
at the end -- had to postpend that to get github to load it & and of course remove the description pre-config.toml
)failing_key_remapping-config.toml.txt
Reproduction Steps
Highlighted and annottated remapping images attached.
The
config.toml
file also attached so one can just switch that in and drive it themself.Helix log
~/.cache/helix/helix.log
Platform
macOS 12.5
Terminal Emulator
iTerm_2 3.4.15 && wezterm 20220624-141144-bd1b7c5d
Helix Version
helix 22.05 (27609f5)
The text was updated successfully, but these errors were encountered: