131–140 of 167 posts
All the tree-sitter features and datastructures seem ideal for a query language to be bolted on - something that generalises beyond symbol search or “find all references” - guess since there’s an API this is a DSL for writing queries about your code.
Does something like this exist?
Very detailed explanations. I learned a bunch about the syntax highlighting and code understanding in Helix & friends just from reading this. All the tree-sitter features and datastructures seem ideal for a query language to be bolted on - something that generalises beyond symbol search or “find all references” - guess since there’s an API this is a DSL for writing queries about your code. Does something like this ex…
Very detailed explanations. I learned a bunch about the syntax highlighting and code understanding in Helix & friends just from reading this. All the tree-sitter features and datastructures seem ideal for a query language to be bolted on - something that generalises beyond symbol search or “find all references” - guess since there’s an API this is a DSL for writing queries about your code. Does something like this ex…
zed uses tree-sitter and has a powerful query engine (dsl is lisp scheme): https://zed.dev/blog/syntax-aware-editing#tree-queries
Earlier quoted context omitted.
For me, the issue isn't that I'm unwilling to learn new things. It's that I cannot use these keybindings anywhere else. Almost all online editors and workstations have some sort of vim keybindings. When I ssh into a Linux machine I can trust it has vim editor. It's like qwerty keyboard, I'm sure that there's better layouts but I just cannot discard the flexibility of being able to jump on most machines and be 99% pro…
Honestly, I don't think this is a big deal. I use helix as my primary editor, but when I'm on another machine and it only has vi or whatever I just use that and I can mentally switch to using the vim keybinds with little issue. Like sometimes I'll mistakenly `m-i-w-c` instead of `c-i-w` or `d` instead of `x`, but then I just hit `u` and continue.
Earlier quoted context omitted.
personally i just find verb noun editing a tiny bit more fun than noun verb. you craft an incantation that either does everything right or backfires. there’s no feedback while said incantation is being constructed. practically, noun verb is much better of course.
I think noun-verb is worse; I'm unsure where the idea comes from that Helix's (or Kakoune's) editing model is better. Bear with my short rant. :-) I don't want or need pre-emptive visual feedback on every keystroke, because it's a tool I use every day. I want an editing language that allows me to develop a mental model of it, so that I can _avoid_ round-tripping most edit actions visually. The primary advantage of th…
I have mixed feelings about Neovim adopting multicursor. Doesn't setting multiple cursors and then acting on them belong in the noun-verb camp? Unless you call it multivisual, of course!
Earlier quoted context omitted.
surprised helix doesn't support the . key - is that incompatible with its interaction model somehow?
Yes, its model is that you make a selection and then act on it. After the action happens there's nothing selected. The editor can't infer your intent in making the selection, so there's no reasonable notion of repeating the last edit. You can separately repeat the last motion or last action, but not the whole edit---which of course isn't as useful. Helix would _ideally_ like you to tell it ahead-of-time everywhere yo…
Earlier quoted context omitted.
personally i just find verb noun editing a tiny bit more fun than noun verb. you craft an incantation that either does everything right or backfires. there’s no feedback while said incantation is being constructed. practically, noun verb is much better of course.
I think noun-verb is worse; I'm unsure where the idea comes from that Helix's (or Kakoune's) editing model is better. Bear with my short rant. :-) I don't want or need pre-emptive visual feedback on every keystroke, because it's a tool I use every day. I want an editing language that allows me to develop a mental model of it, so that I can _avoid_ round-tripping most edit actions visually. The primary advantage of th…
Helix is great and includes a lot of stuff out of the box (file pickers, syntax highlighting, linting etc) without any configuration or installing plugins (contrary to vim or neovim). I would definitely use it but the main disadvantage is that some keybindings work differently than vim. I understand that the keybindings may be better that the vim ones but after years of using vim I expect "x" in normal mode to delete…
Congrats! I am happy for helix but i don't think it's a good fit for me. I use Neovim. It does what i want it to do. It's one of the best available options. But, i am not completely satisfied with it. I personally want an editor with following: * Modern codebase. Written from scratch. * VIM Keybindings: I have muscle memory of Vim. I would like to use Vim Keybindings in my editor. I don't want to use any other keybin…
Earlier quoted context omitted.
Here is the forum post that convinced me NOT to continue getting into Helix. It says all I need about the project health. And given the development since then, I am more confident that it’s a bad horse to bet on. https://github.com/helix-editor/helix/issues/1840#issuecomme...
I don't see the problem. It's a great result: (paraphrasing) "people arguing about whether code folding is useful or not is pointless. we're going to do it eventually but not right now." What's wrong with that?
Still, I wasn't especially impressed with "code folding is hard, we might do it one day but don't hold your breath" from an editor that purports to be a replacement for vim or neovim.