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.

For some time now, my KeepassXC browser extension keep informing that I’m using older version of KeepassXC I usually upgrade immediately, so I did. Or so I thought.

I saw the same warning couple of days later. I thought there was new version, but there wasn’t. So installed it again.

This happened one more time, and I realized that even after upgrade, KeepassXC remained at older version (2.66, but as you’ll see it doesn’t matter)

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.

Following those instructions, I was able to get “up and running”

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. After some time, I ended up subscribing to Vim Telegram group, and asked about better neovim GUI.

I just looked at the last post here. It was in late Feb 2022 I just realized that I have not posted anything in entire of March 2022

The reason for this microblog was to make it low-friction so that it does not go the way of my other blogs with month(s) long and sometime year long silence. But then why didn’t I post anything here for a month ?

I started working with a startup that is bigger than ones I was working with last decade or so. and they have processes, and meetings.

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.

Today was my last day at stck.me (Formerly Scrollstack.com) I spent more than a year working with the wonderful engineering team there. I learnt a lot from everyone on the team, and made some new friends (I already knew a lot of folks from this team before I joined) during my stay.

I will continue to cheer stck.me from the sidelines

Some of my contributions during my time with scrollstack:

• Improve the SEO of the hosted blogs by auto generating the Sitemap from the posts
• Integrate Honeybadger error monitoring tool for proactively addressing the issues in production setup
• POC to generate PDF from Post Source
• Multiple file support for Digital Goods like Gumroad
• Monthly Active User Metrics. Although we did not end up using it, I learnt about rsyslog and logrotate in the process
• Refactor tiptapy to use more Jinja and less python. This helped reduce the python code. Shekhar helped a lot on this process. 🙏