Why not a vim plugin
> Note that the Ki keybindings cannot be simply implemented in Vim/Helix via key- remapping, due to the lack of the concept of Selection Mode, and implementing that requires major architectural changes in the core.
Ki Editor - an editor that operates on the AST
21–30 of 154 posts
Re: Ki Editor - an editor that operates on the AST
#22Have you seen any of the lisp tree editing modes for eMacs or vim?
Re: Ki Editor - an editor that operates on the AST
#23Earlier quoted context omitted.
That comparison table is strange and sometimes wrong. Neovim for example detects and updates external file changes by default. And the coherence of the keybindings in Ki is "Great" bit vim/helix: > As you can see, there's no single logical categorization for these keymaps, they are either lowercase-uppercase, normal-alt, left-right bracket, or outright unexplainable. Word, End, Back, Change Word and even Change Inner…
> It shows the creator comes from VSCode Hey, one of the creators here, I actually daily drove Neovim for two years, before switching to Helix for a while, then finally Ki. > multi-cursor is a useless feature I was a Neovim macro user until I figured out how insane that was compared to multi-cursor after using Helix.
> I was a Neovim macro user until I figured out how insane that was compared to multi-cursor after using Helix.
Multi-cursor was the first plugin I installed when I moved from VSCode to Vim because I was used to hitting Ctrl+d to select all words and then replacing. Does Helix do something different?
1) First I reach for for visual block selection if everything is neatly aligned.
2) Next choice is %s/search/replace(/c if I need confirm).
3) Macros, and I love it everytime I get to use them. I just record the movements, copy what I need to copy, paste it where I need to paste it, and it's repeatable for every line or block where the *formatting* matches. And this is the important part, the words don't matter. I still feel like a wizard using them.
As far as I understand multi-cursor option 3 is a no-go without macros if the words don't match. But macros don't care as long as the movements translate to the same edits. How does Helix multi-cursor work that make macros insane?
Re: Ki Editor - an editor that operates on the AST
#24Earlier quoted context omitted.
That comparison table is strange and sometimes wrong. Neovim for example detects and updates external file changes by default. And the coherence of the keybindings in Ki is "Great" bit vim/helix: > As you can see, there's no single logical categorization for these keymaps, they are either lowercase-uppercase, normal-alt, left-right bracket, or outright unexplainable. Word, End, Back, Change Word and even Change Inner…
> It shows the creator comes from VSCode Hey, one of the creators here, I actually daily drove Neovim for two years, before switching to Helix for a while, then finally Ki. > multi-cursor is a useless feature I was a Neovim macro user until I figured out how insane that was compared to multi-cursor after using Helix.
I still think their point about search and replace still stand though. I make most my edits with regex in neovim nowadays and I feel this is the superior paradigm: You don't even need to get to some specific location in order to edit it. I also almost only use search to move around the file and I can even reuse the searches for substitutions. It makes most vim motions and commands almost useless for me nowadays.
I also feel like macros are a more clunky and error prone way to do what substitutions can do. Almost never use them.
Re: Ki Editor - an editor that operates on the AST
#25The "First-class syntactic selection" reminds me of my most used shortcut(s) in Jetbrains IDEs: the Expand / Shrink Selection. Ctrl + W Ctrl + Shift + W https://www.jetbrains.com/help/idea/working-with-source-code... It really changed my perspective on interacting with the 'text' of a file. VS Code, Zed, etc. have similar operations, but in my experience they expand and shrink too coarsely.
This has got to be my favourite feature of IntelliJ, along with the dumb context actions menu
Re: Ki Editor - an editor that operates on the AST
#26[dead]
Re: Ki Editor - an editor that operates on the AST
#27Earlier quoted context omitted.
> It shows the creator comes from VSCode Hey, one of the creators here, I actually daily drove Neovim for two years, before switching to Helix for a while, then finally Ki. > multi-cursor is a useless feature I was a Neovim macro user until I figured out how insane that was compared to multi-cursor after using Helix.
> I was a Neovim macro user until I figured out how insane that was compared to multi-cursor after using Helix. Multi-cursor was the first plugin I installed when I moved from VSCode to Vim because I was used to hitting Ctrl+d to select all words and then replacing. Does Helix do something different? 1) First I reach for for visual block selection if everything is neatly aligned. 2) Next choice is %s/search/replace(/…
Sorry for derailing a bit, the search and replace using a query make sense for purly textual (non-syntactic) editing, but if you want to apply consistent syntactic modifications across multiple locations in the same file, you will need both multi-cursor and syntax node selection/navigation/modification.
It's hard to explain unless you actually try Ki, because it is a paradigm shift
Re: Ki Editor - an editor that operates on the AST
#28In my classification of editors: 1. Orthodox. Mostly focused on looks and integrations. 2. Modal, Vim improvement. Focus on keeping basic Vim keybindings with minor improvements. 3. Modal, rethinking Vim approach. Ki falls into the third category which I constantly monitor.
Exactly the same for me. So far, there have been many challengers but the same champion (subjective, I know).
Re: Ki Editor - an editor that operates on the AST
#29Earlier quoted context omitted.
> It shows the creator comes from VSCode Hey, one of the creators here, I actually daily drove Neovim for two years, before switching to Helix for a while, then finally Ki. > multi-cursor is a useless feature I was a Neovim macro user until I figured out how insane that was compared to multi-cursor after using Helix.
I still think their point about search and replace still stand though. I make most my edits with regex in neovim nowadays and I feel this is the superior paradigm: You don't even need to get to some specific location in order to edit it. I also almost only use search to move around the file and I can even reuse the searches for substitutions. It makes most vim motions and commands almost useless for me nowadays. I al…
Yeah, macros are definitely helpful at times, but not as much as one might think.
I think the same goes for multi-cursor, though.
Re: Ki Editor - an editor that operates on the AST
#30In my classification of editors: 1. Orthodox. Mostly focused on looks and integrations. 2. Modal, Vim improvement. Focus on keeping basic Vim keybindings with minor improvements. 3. Modal, rethinking Vim approach. Ki falls into the third category which I constantly monitor.
4. All of the above. Which is Emacs.
Right, but we are discussing editors here.