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:
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 😄
I started this blog using indiefeed theme. But soon realized that the original creator has moved on. They have marked the repo as read-only on github. I had already started tweaking it to my liking, but now changes are more than tweaks. e.g. The original theme did not have good image support. i.e. only images used were in the Author profile image, and it has rounded corners/circular shape, which does not work when image is part of the post itself.
Continuing with my Ruby language learning journey, I wanted to use it for more than Hello world.
So I decided to try python’s request equivalent.
Since I didn’t know where to begin, I just searched for requests on RubyGems
Turns out Gem by the exact name exists and with description Because Requests for Python is awesome 🤗 But it isn’t updated in close to 5 years now.
I also wanted to use something native (i.
I published my new sketch This appeared on the back of one of the children’s books. I think tinkle
It took me less than 5 minutes, but makes for a good break from work, and lets me keep practicing my art.
The girl appears so happy showing off her new dress (I think) or she is just happy and frolicking. In either case, it is adorable.
If you haven’t, you can check my older sketches here
While there are multiple ways to use Ruby debugger, for my first Ruby script (?) I found starting the script via rdbg to be the easiest.
Like rdbg myscript.rb
Debugger has all the basic command I have used elsewhere.
n for next pp for pretty print q for quit For subsequent times, using require 'debug' followed by binding.break may be better.
This README has all the details.
If I were to explain bundler to pythonista (like myself) I would say
Bundler in Ruby land is like poetry in python land, except it does not create sandbox environment
To explain it a little more. It tracks dependencies in a Gemfile (and Gemfile.lock) which then goes in your repo. Other engineers sharing your code would then run bundle install, and they get exact same Gems (including versions) on their machines.