I want a vi layer for helix. I don't want to have any vimrc configuration, just open my editor and have LSP and everything working immediately. I just can't figure out how to switch to helix keybindings.
[deleted]
The extensible vi layer for Emacs
11–20 of 104 posts
Re: The extensible vi layer for Emacs
#12A light bulb went off in my head, is Neovim able to use Emacs as a GUI yet? Why emulate VIM in 2023 when you can just become a GUI for it. I'm still waiting for JetBrains to wake up from sleeping at the wheel and implement a Neovim client for their IDE core.
It's kinda embarrassing, JB wants to push their new editor, but even months after public beta, the vim emulator is still barely usable, and afaict it's maybe like 1-2 people working on this. I don't get it, if you are targeting developers, why is it that having Vim keybindings not a top priority? Or am I living in my own circle? https://youtrack.jetbrains.com/issue/FL-10664
My thinking is, if you focus heavily on letting your editor be a client for Neovim, you now can pull in all the stubborn VIM users easily. "Look! It behaves the most like vim that any editor you've ever used does!"
I fully agree with you. I'm not sure why they're asleep at the wheel.
Re: The extensible vi layer for Emacs
#13A light bulb went off in my head, is Neovim able to use Emacs as a GUI yet? Why emulate VIM in 2023 when you can just become a GUI for it. I'm still waiting for JetBrains to wake up from sleeping at the wheel and implement a Neovim client for their IDE core.
It's kinda embarrassing, JB wants to push their new editor, but even months after public beta, the vim emulator is still barely usable, and afaict it's maybe like 1-2 people working on this. I don't get it, if you are targeting developers, why is it that having Vim keybindings not a top priority? Or am I living in my own circle? https://youtrack.jetbrains.com/issue/FL-10664
You may very well be living in your own circle. My anecdata is that most engineers use VSCode these days. In my current organisation I am the only person that uses Emacs that I am aware of (and I use evil-mode). I know a handful of people use (n)vim. But by far the most common editor I see being used is VSCode.
Re: The extensible vi layer for Emacs
#14Just use vim. Yes, emacs has a lisp engine, but so does nvim[1]. Really, though, using vim properly means that it doesn't need to swallow the kitchen sink[2]. Just use vim. 1: https://github.com/Olical/aniseed 2: https://blog.djha.skin/p/emacs-users-im-okay-i-promise/
Neovim isn't emacs, and you can't make it emacs no matter how hard you try
- Emacs is writen mainly in lisp, neovim has a lot of c. You don't have to worry about if something is possible in emacs, you can just hack onto it, on neovim you have to spend an awful lot of time seeing if something is possible
- Emacs has decades of ecosystem, neovim does not
- Emacs is build on lisp and has first class support, fennel is a second class citizen in neovim, users are exepcted to (rightfully) figure their own way through things. Whereas the internet is full of decades of elisp knowledge
- Emacs is a proper GUI. neovim is not, yet.
In the future, can neovim match and exceed emacs? yes. Is it capable of it? yes.
It however, is not currently is not an emacs replacement in any way shape or form. It is an entirely different editor, with a different way of going about things, and should be treated as such.
This is coming from someone who often contributes to neovim and neovide (a neovim GUI), and uses fennel both inside and outside of neovim extensively.
Re: The extensible vi layer for Emacs
#15I used that settings for a few years, then tried to move entirely to vim, and now I'm very happy with vscode + vim.
I like vim as a touch typer, I think it's a setting that minimize end motions. It's also very convenient in the terminal. On the other hand, I think it's not convenient as an IDE: too many shortcuts, clumsy integration with LSPs, especially when you need to work with different languages.
For me it works best as a light, universal, editing mode on top of a modern solution for an IDE. That being said, I wonder if I wouldn't be better off moving away from vim entirely and get used to a simple setting which works straight out of the box.
Re: The extensible vi layer for Emacs
#16A light bulb went off in my head, is Neovim able to use Emacs as a GUI yet? Why emulate VIM in 2023 when you can just become a GUI for it. I'm still waiting for JetBrains to wake up from sleeping at the wheel and implement a Neovim client for their IDE core.
Its certainly possible, though useless.
Most vim emulation plugins struggle with accuracy, EVIL exceeds it. Manly due to evil-collection and various other packages, pretty much every emacs package has evil support, and that integration feels very native to emacs
This is a case where being a neovim gui would be worse. Though, someone could totally do it for shits and giggles.
Finally, that operating system would have a decent text editor :)
Re: The extensible vi layer for Emacs
#17I used that settings for a few years, then tried to move entirely to vim, and now I'm very happy with vscode + vim. I like vim as a touch typer, I think it's a setting that minimize end motions. It's also very convenient in the terminal. On the other hand, I think it's not convenient as an IDE: too many shortcuts, clumsy integration with LSPs, especially when you need to work with different languages. For me it works…
NeoVim has got native LSP support, and works pretty well for me out-of-the-box for most languages. LSP servers need to be installed externally, but I hope they manage to bundle them somehow in the future. LunarVim already provides automatic LSP server installation.
Re: The extensible vi layer for Emacs
#18Just use vim. Yes, emacs has a lisp engine, but so does nvim[1]. Really, though, using vim properly means that it doesn't need to swallow the kitchen sink[2]. Just use vim. 1: https://github.com/Olical/aniseed 2: https://blog.djha.skin/p/emacs-users-im-okay-i-promise/
Neovim isn't emacs, and you can't make it emacs no matter how hard you try - Emacs is writen mainly in lisp, neovim has a lot of c. You don't have to worry about if something is possible in emacs, you can just hack onto it, on neovim you have to spend an awful lot of time seeing if something is possible - Emacs has decades of ecosystem, neovim does not - Emacs is build on lisp and has first class support, fennel is a…
As I said, If you're trying to use vim like emacs, you're doing it wrong. You can and people do, but that's not the point. See my second link on the subject.
Re: The extensible vi layer for Emacs
#19I used that settings for a few years, then tried to move entirely to vim, and now I'm very happy with vscode + vim. I like vim as a touch typer, I think it's a setting that minimize end motions. It's also very convenient in the terminal. On the other hand, I think it's not convenient as an IDE: too many shortcuts, clumsy integration with LSPs, especially when you need to work with different languages. For me it works…
NeoVim has got native LSP support, and works pretty well for me out-of-the-box for most languages. LSP servers need to be installed externally, but I hope they manage to bundle them somehow in the future. LunarVim already provides automatic LSP server installation.
Neovim also has a server mode that lets it be used to drive other editors, so you can get the best of both worlds.
Re: The extensible vi layer for Emacs
#20Emacs also has a vi layer built in: viper mode.