Ki Editor - an editor that operates on the AST
ki-editor.org
Ki Editor - an editor that operates on the AST
1–10 of 154 posts
Re: Ki Editor - an editor that operates on the AST
#2Vim-like (terminal and VSCode extension) that prioritizes syntax-based navigation.
Comparison to Vim and Helix: https://ki-editor.org/docs/comparison#user-content-fn-1
Re: Ki Editor - an editor that operates on the AST
#3In 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.
Re: Ki Editor - an editor that operates on the AST
#4In 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.
Re: Ki Editor - an editor that operates on the AST
#5In 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.
Vim is Emacs applied to Vi
Re: Ki Editor - an editor that operates on the AST
#6In 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.
I know, I use Emacs+Evil.
I'm going to give Ki a try and, in case of success, to think about writing Ki binding for Emacs.
Re: Ki Editor - an editor that operates on the AST
#7The "First-class syntactic selection" reminds me of my most used shortcut(s) in Jetbrains IDEs: the Expand / Shrink Selection.
Ctrl + W
Ctrl + Shift + W
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.
Re: Ki Editor - an editor that operates on the AST
#8The "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.
Also available as `incremental selection` in Neovim via tree-sitter.
Re: Ki Editor - an editor that operates on the AST
#9Vim-like (terminal and VSCode extension) that prioritizes syntax-based navigation. Comparison to Vim and Helix: https://ki-editor.org/docs/comparison#user-content-fn-1
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 (, etc are very logical to me and I feel like I'm talking to the editor when editing. I get that it doesn't make sense when one has learned another way to do it, but it does make total sense you just have to make an effort to try and understand it.
It's like learning and always driving automatic then calling manual "outright unexplainable". You simply learned another way and are conditioned into believing that's the one true way. It shows the creator comes from VSCode (multi-cursor is a useless feature, just use s/search/replace and get used to macros and a whole new world will open).
Re: Ki Editor - an editor that operates on the AST
#10In 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.
This is the first time I've heard about Emacs trying to look nice.