Inspired by the #Indieweb and #Emacs carnivals, I wanted one about #Vim / #Neovim, and here it comes. It will start in September, so you have two weeks to think, and blog about it.

#editor #terminal #writing #blog #blogging #fediverse #mastodon #carnivals

#100DaysToOffload : 85/100

https://lazybea.rs/vim-carnival-202509

One of the advantages of using vim is that you can finish typing most of your rants with :q!
... and loop as many times needed /s

#vim #neovim #therapy

Recently started learning #morsecode , although it's completely useless to me. Sometimes it helps to understand why things developed like they did when you go back in time, when remote communication started. And I love having a #lowtech fallbacks.

It's like learning #ed in order to understand concepts of #vim.

The more I think about it, the more it seems to me that in this day and age with all the modern threats having a text editor that is capable to not only connect to the Internet, but also install some code packages from repositories (and probably do dependency resolving) is a recipe to catastrophe. Sooner or later.
It's probably one thing when you use a curated list of half a dozen addons that you can even personally peruse (or even contribute to). It's a whole other thing when you use some huge "distro" with probably hundreds of packages that also receive constant updates you cannot possibly control.
It's mostly about #Emacs, of course, but #vim is fully capable of it too. I won't even mention the likes of #VSCode.
We had a fair share of supply chain attacks in the recent years (npm, pip, even xz in some way). No reason to think no one's gonna use this channel of attack.
Maybe it's just my fibs. But there is some uneasy feeling about the fact that you edit, perhaps, extremely private, personal or sensitive texts while your editor runs some background code doing who knows what. It's one thing to trust people who wrote vim or Emacs and a whole other thing to trust a hundred other unknown parties at the same time.

Dumb #vim trick:

Have a bunch of files open in multiple windows and want to jump to the first (or last) line in all of them?

:windo 1

or

:windo $

and done.

If you use tabs instead of windows, you could use :tabdo instead.

or you can jump to the next instance of /pattern/ in all open windows/tabs with

:windo /pattern
:tabdo /pattern

or the first/last (assuming you have 'wrapscan' set) with

:windo $/firstpattern
:windo 1?lastpattern

https://4c6e.xyz/nvi.html

It’s not meant to be exhaustive, just a practical guide to help get things done with a lighter touch.

#nvi #vi #vim #minimalism

Ok. Day one of using @silverbulletmd in #Vim mode lead to already fixing some ugly UI glitches. Now thinking how to expand #Lua APIs to define Vim commands, bindings and other things. Also a reason to dive a bit deeper into @neovim which leans heavily on Lua. Also an interesting source of inspiration for Lua API design potentially.

Although familiarity with usual vim still comes in handy on the school computer 😅

Oddly tempted to try to switch to #Vim (realistically @neovim ) again for code editing. And switching on vim mode in @silverbulletmd

Trigger: the realization that anything not purely open source (like VS Code) eventually #enshittifies