Replies: 2 comments 2 replies
-
The issue is that you viel the cursors as a bar instead of a Block. Helix used Block cursors semantica, where (even in insertmode) the cursors always has width one. So we don't highlight the brackets to the kwft of the cursors or to the right of the cursors but the bracket at the cursors. It would be weird to apply the matching brackets highlight anywhere but the cursors itself. I don't think we will go forward with that |
Beta Was this translation helpful? Give feedback.
-
Conceptually, it's odd. In practice, it's quite useful. When I type a close brace in insert mode, I want to see immediately which open brace I'm matching. I don't want to move left one character, confirm the delimiter, then move right and keep typing. Emacs has this, as does kakoune (as I think this should be a configurable option, defaulting to false if you like, and independent of cursor shape. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
In the editors I'm used to (neovim, vscode), when in insert mode, the pair highlighting highlights the sibling of the pair to the left of the cursor when there is one, but helix seems to do the opposite.
This is probably easier to demonstrate with an example (
|
is the cursor)or
Currently, helix seems to not highlight any of the parens in these situations. I find this very annoying, because I often use the pair highlighting to figure out if I need to add more parens. Here I have to guess or exit insert mode to check.
Of course, this becomes a bit ambiguous with matched parens, which neovim highlights like this,
but helix like
but for that to be intuitive, the highlighting needs to highlight both pairs (#8489)
Beta Was this translation helpful? Give feedback.
All reactions