read the man pages

me

Mtende Kuyokwa

29 March, 2025

The magic you are looking for is in the work you are avoid

~ Dipen parmar

In a recent read, OSTEP —operating systems in three easy steps—, I came across the phrase RTMP — read the man pages— for when someone asks basic questions that were already dissolved in the manual. It reminded me of how I dodged reading the nvim user manual. Just like Rust has its documentation to be read offline, so does nvim. For rust it is in the browser whilst nvim it is in the lovely terminal.

In Rust, you fire the book up by running.

$ rustup doc --book

In vim you simply

:h user-manual

Exploring the man

When using Vim, I try to do everything with the least amount of keystrokes. A moment where keystrokes where wasted is when I used CTRL-U to look for where I last edited especially if the text is not unique enough to use search. I discovered I could use CTRL-I and CTRL-O to jump around which is cool and keeps the keypresses to a minimal. Another cool thing I discovered was that for EJS —the templating engine— one could change the filetype to HTML so that you get syntax highlighting and utilize the HTML LSP since EJS does not have one.I might sound dramatic but I stood up and applauded after finishing this sub-chapter.

:setfiletype=html

I still do not recommend reading the man pages as soon after reading :TUTOR because newly learnt nvim motions will be forgotten without practice as you spend more time learning about them than using them. Practice builds game.

Purists and community

A Purist is someone who has a traditional way of doing things and enforces it on others. I would say in the nvim community

"Do not use lazyvim until you can create your config from scratch"

is one common purist comment just as

"no doom-emacs until you can create a config in vanilla-emacs"

. I hated this statement because I used lazyvim soon after finishing vim-tutor. After reminiscing, I have realized that I lack skin in the game with nvim and If I were to contribute to it I wouldn't know what to do because I hardly understand its internal philosophy. There is no dodging the ball. It might seem as if you are slowing down building it from scartch but it pays off in the long run. I am planning to work on mine from scratch —not kickstarter.nvim— this weekend and see how it goes.

Kitty litter

A couple of weeks ago, I picked up rust for school. One thing I try to do when I am learning something new, is to surround myself with the technology to reduce procrastination. In the wake of this habit, I migrated from kitty to the rust's wezterm. wezterm is nice in terms of configuring with Lua but Kitty is faster on my hardware so I had to go back. This statement is just a note if there is a terminal war anywhere, kitty is 0.06ms faster.

Happy hacking !! P.S, new neovim 0.11 looks nice can't wait to try it out