Today I spent some time getting projectile equivalent working with LunarVim
At first I went with builtin/core plugin projects.nvim. Enabling it was quite straight forward. I wasn’t sure how to add new project.
Then I tried telescope-projects. Even here I could not add new project (Per their documentation, it is Ctrl-a in Insert mode, and just c in normal mode) But I just opened the project root I wanted to work on, and it got added to the list of projects.
Once I got Neovide working with LunarVim, I realized that I had not updated LunarVim for a long time.
I was already in rolling branch, so I did git pull origin rolling
Big mistake.
Things broke.
After RTFM, I noticed that there is :LvimUpdate command in LunarVim.
But by this time, my config was so broken that nothing worked 😞
Luckily, I found the old instructions that helped me initially.
So I tried VimR for some time, but it always felt odd. Sure all the LunarVim keybindings worked. But VimR wasn’t just Neovim client. It comes with its own features like the side panes for Files, Buffers, Markdown etc.
Also, it won’t really quit. :q! would destroy the window, but it would remain in the dock.
So for main work, I used Emacs.
Then today in Doom Emacs Telegram group, someone started talking about Vim.
I had almost given up trying to use lvim config with GUI. But I persisted (and pestered folks on github issue 🙂) Finally, I got it working.
I wrote about How to get VimR to use Lunarvim configuration so that others can also benefit from it.
After setting up LunarVim, I wanted to get it to work with a NeoVim GUI
I had tried some in the past, but did not like any.
Then (I think on Discord) I came across some discussion that they got LunarVim (lvim henceforth) to work with Neoclide.
I couldn’t even get it to run 😞
I tried VimR, and it worked. i.e. I got it running. But I didn’t like their default look.
After my problems with Doom NVim, I decided to go back to LunarNVim.
I had never really left, but since both Doom and Lunar are NVim based configurations, they may overwrite the configurations (like from ~/.local/share/nvim/)
So I completely removed both Doom and Lunar and reinstalled.
I also installed ltex LSP for makrdown, which I could not do with Doom Nvim.
My other requirement was projectile equivalent. I found that there is :Telescope projects built-in with Lunar.
Just I was getting excited about Doom NVim, today I read (on their Discord server) that Alejandro aka NTBBloodbath on github has lost interest in Doom Nvim
To quote him :
I’ll slowly try to finally make Emacs my primary code editor (always failed in each attempt haha), Neovim’s ecosystem isn’t going in the direction I would like and I think it never will be so I’m very frustrated and sad with it.
Those who know me, probably already know that Doom Emacs has been my daily driver for a last years now.
and that recently neovim has piqued my interest.
I already wrote about Lunar NVim
Today I discovered Doom-Nvim
Port of (sorta) Doom emacs to neovim ecosystem.
What is not to like ? 😄
As I wrote in Lunar NVim post, I am happy with Doom emacs. But this might make me switch back to (n)vim 😄
As I mentioned earlier, I’m trying Lunar nvim starter kit. Latest version of nvim comes with LSP support, and while learning a new language LSP could be really helpful (I think)
I had heard of solargraph. Running :LspInstall in nvim gave me option of sorbet as well. But I decided to stick with solargraph.
nvim was successful in installing solargraph, or so it told me. But it did not work. LspInfo told me that it did not find solargraph Just to be sure I gem install solargraph from the terminal, before I tried to install LSP from nvim again
I came across some starter kits for nvim. Earlier I tried adding individual plugins and learning all the nvim basics, but since I’m pretty happy with Doom Emacs 1
But Lunar nvim seems stable and provides a lot of functionality out of the box. 👍
prerequisite page asks to ensure that I have cargo. I knew it a package manager(?) for rust, but didn’t know whether I could install it standalone.