Obsidian has vim keybindings

Today I discovered that Obsidian supports vim style keybindings out of the box. But it knows that vim is not for everyone. So it checks whether you know what you are doing (when you enable the setting, which is OFF by default) by having you enter a command in a pop up 😄 TBH, one can easily find out that command and “cheat”. On the other hand, if you don’t know vim, and still want to turn on the setting (by cheating) - you deserve what you get 😄

Continue Reading »

Magit fixed

As I wrote earlier, I was unable to use magit because of the third party issue. Doom fixed it within hours (bigger community) But minmacs also fixed 1 it (only one person) I had to follow a slightly complex set of instructions, but I’m glad it all worked out in the end. I will continue to use Minemacs on my personal machine. Working in markdown is pleasure in minemacs. I want to get robe working with minemacs, and codium and chatgpt

Continue Reading »

Back to Doom : For work

I updated Minemacs few days ago, and it broke magit 😱 1 I had suspected that it is not problem with Minemacs But I can’t have magit broken, so on my work machine I switched (back) to Doom FWIW, the issue is already fixed on Doom 2 This time I noticed doom now installs itself under ~/.config/emacs rather than ~/.emacs.d I also updated my init.el and config.el Now that I’m back, all my muscle memory started kicking in.

Continue Reading »

→ Zed Editor

My colleague told me about this new editor written in rust yesterday. The feaure page mentioned vim-mode, so I was OK to try it.

It seems collaboration is their USP - I don’t see using that feature personally anytime soon.

So what about rest of the features ?

My first impression is that it can be light alternative to VSCode. It has similar UI structure, default keymap as VScode. It supports few languages Out of the box, Ruby being one of them, so I may try it at work as well.

Coming back to vim-mode - the reason for which I even was ready to try it. It was not easy to enable it. I had expected to find it under keymap.

But vim-mode is restricted to modal editing, so one needs to enable it via settings.json (similar to VScode) and set "vim-mode": true there. Other things - not related to modal editing, but I have come to rely upon - like : commands to save (:w), or :1 to jump to the beginning of the file, do not work.1

Opening new file wasn’t intuitive. It closed the existing file. There is no New tab either.

But after adding the folder to the project and opening anotehr file from the same project, opened it in separate tab. 😌

In conclusion :

  1. Good attempt to provide VScode alternative. Because it is a native app, it will be faster than Electron app
  2. This is not meant to be terminal app anyway. So for modal editing in terminal, I will stick to helix

  1. Cmd+S to save the file, and ^G to goto line/column ↩︎


I have written earlier that I’ve started using VSCode occasionally for work. Finding files and find-in-files is much better and faster. But I do miss modal editing. That is where VSpaceCode comes in. VSpaceCode is Spacemacs like keybindings for Visual Studio Code I had come across VSpaceCode almost two years ago I was using VSCodium at that time (hoping it is faster than VSCode - it isn’t - on my old machine) and could not install VSpaceCode.

Continue Reading »

Using VSCode

I installed and used VSCode on office provided MBP yesterday. It is not like I have not used it in past. I tried vscode-vim plugin for modal editing. It allows you to embed neovim in VSCode (So all the configuration of neovim is available here.) But on my old machine, it was slow. (I also tried VSCodium, thinking it might be faster. It wasn’t) I used it exclusively for Dendron (my PKM) cause it is mainly VSCode plugin (While it has command line tools, the main strength is as VScode plugin)

Continue Reading »