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)

I was always fascinated with devices with stylus, where I could draw electronically (Not sure if the word digitally was being used back then.)

My first such device was Palm III.¹ It came with Stylus. That was in the last century.

Needless to say, I stopped using after year or 3. (I had it long time after that, and then I finally gave it for electronic waste/recyling program 😢)

Then after my elder son was born (which has no significance - just that I remember it as such) I purchased Samsung Galaxy Note 8 ²

I purchased myself XP-pen Deco mini 7¹ 🎉

Was debating between this and iPad for so long.

This won, cause :

• Much cheaper
• Can be connected to Android phone, Windows PC or macOS

Initial impressions :

• Feels like writing on a piece of paper (as opposed to, on a glass surface)
• The pen is BIG! (Not used to such big pen or stylus)

Still getting used to various sketching software.

I’ll start with something easy (Started with Autodesk Sketchbook - Big mistake - Got lost)

I used zsh for couple of years, and then switched to fish mainly for its built-in autocompletion.

fish is a modern shell (just like helix) and thus (I think) it does several things differently. For someone using various shells for over 2 decades, resisting muscle memory does not come easy. ¹

I was used to export KEY=value, so in fish I always had to look up How to set an environment variable in fish 😆 - even after 2 years.

I have been using Emacs for several years now. But I switched to (and stayed with) Emacs only because of evil mode.

I had been vi user for decades before that. Even today, I use (Neo)vi(m) occasionally.

Right now, I’m writing this in Helix editor, which is lot closer to modal editing of vi, than of Emacs.

So there.

I am aware that various shell support vi mode, but the default is Emacs.

My previous theme indiefeed supported both light and darkmode. The current one does not.

I’m in the process of fixing that.

But I didn’t know how to test it ? i.e. Depending on the time of the day, Firefox would either select light mode or dark.

Turns out, Developer tool lets you switch it (for that page).

When in Inspector tab, look for icons for Sun (light) and moon (dark).

See the diagram below :

Add something like the following to your css

@media (prefers-color-scheme: light) {
	body {
		background-color: #f0f0f0;
	}
}

@media (prefers-color-scheme: dark) {
	body {
		background-color: #0f0f0f;
	}
}

I’m just learning this. But this above doesn’t look scalable. My previous theme, defined colors as variables, per color-scheme and in the other css, use these variables instead of actual colors.

That way, you need to modify colors only at one place 🎉

See this

D2 allows me to generate diagrams from the same source file using different layouts

It comes with two built-in layout engines :

Dagre is the default :

Other one is ELK This needs to be specified explicitly as :

D2_LAYOUT=elk d2 in.d2 out.svg

and here is the output