This is Zed's official roadmap and progress tracker for porting Zed to Linux. Contributor Guide There's a lot of surface area to cover and we would love contributions for anything from fixing a sma...
If only Helix would have vim mappings and a plugin system, it would kill neovim over night…
In it’s current state, it’s only suitable for people who don’t need any plugins. So if you want a plugin for picking a virtual environment in python for example, you just can’t do it in Helix.
I don’t know, to me it’s really limited without any form of plugins. I truly wish it had a plugin system because tons of people would write high quality rust plugins.
That’s a weird way to look at the projects, in my opinion (“if only X had Y, it would kill Z…”).
Helix and Neovim have different approaches to editing, configuration, etc. They don’t need to be competing for users. Neovim can exist for the people who want an editor with Neovim’s ideas, same for Helix, and that’s just fine.
Vim and helix have different keymappings for the same tasks, for example to delete a word, helix you type wd, but in vim you type dw. As a vim user of like 6 years, I prefer the helix bindings after understanding them. But the reason I say helix having vim bindings would defeat the point is that if you want vim bindings, just use vim or neovim with plugins. Those are both mature projects that will serve people who want vim bindings better, either switch to helix all the way, or don’t imo
I think it’s possible to remap Helix to be almost (if not completely) Vim-like. I got it to be (I think completely) Kakoune-like with like 15 lines in my config.
If only Helix would have vim mappings and a plugin system, it would kill neovim over night…
In it’s current state, it’s only suitable for people who don’t need any plugins. So if you want a plugin for picking a virtual environment in python for example, you just can’t do it in Helix.
I don’t know, to me it’s really limited without any form of plugins. I truly wish it had a plugin system because tons of people would write high quality rust plugins.
That’s a weird way to look at the projects, in my opinion (“if only X had Y, it would kill Z…”).
Helix and Neovim have different approaches to editing, configuration, etc. They don’t need to be competing for users. Neovim can exist for the people who want an editor with Neovim’s ideas, same for Helix, and that’s just fine.
Helix having vim mappings would defeat the purpose. But once you do
hx --tutorit’s super easy and intuitive coming from vim/nvimWhat means “vim mappings”? I only ever used helix so I supposed it has the same key bindings as vim?
Not really. Helix is closer to Kakoune which is based on the modal editing of Vim but reimagined a bit.
Vim and helix have different keymappings for the same tasks, for example to delete a word, helix you type wd, but in vim you type dw. As a vim user of like 6 years, I prefer the helix bindings after understanding them. But the reason I say helix having vim bindings would defeat the point is that if you want vim bindings, just use vim or neovim with plugins. Those are both mature projects that will serve people who want vim bindings better, either switch to helix all the way, or don’t imo
I think it’s possible to remap Helix to be almost (if not completely) Vim-like. I got it to be (I think completely) Kakoune-like with like 15 lines in my config.