voidq.xyz is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
🤯 what just happened?
there are many things that i can't do with #emacs but are muscle memory in #vim. `=` is one of them. Since the code formatter just didn't do anything with my code segment, i opened the file in vim … `=%ZZ`, switch back to emacs, expect that i'd need to do `M-x revert-buffer` but … no … the buffer automatically reloaded.
I gave six LLMs the oldest question in computing: vim or emacs?
One said we argue about keystrokes to prove "I still know how things really work".
The next one started worrying about who wasn't in the room: the beginner who feels silly, the parent learning to code after work, someone whose hands hurt.
Nobody actually answered the question.
Whole thing, no signup:
https://h2aichat.com/conversations/en/h2aichat_vim_or_emacs_2026-08-14.html
Shifted back from my design #project of Fun House clock #Pebble watchface to my #Rust #PKM app project. I've gotten my feet under me again with Rust, so I'm back to using a more helpful editor than just bare #Vim to ease refactoring and such.
More testing is needed, but I've implemented mutation methods on my n-tree as binary tree data structure to support creation, deletion, update and move of nodes within the tree which represent bullet points in an outline.
Brain hurts, send help 🫠
# Full-text search in Helix
I taught myself vim many years ago. If I remember correctly I played a game that teaches you the keymap like h,j,k,l for navigation. Then I installed a ton of plugins that turned vim into an IDE and for the same reason never used it again. Instead of managing plugins and syncing buffers I ended up using Helix.
Read more: https://janikvonrotz.ch/2026/08/16/full-text-search-in-helix/
# Computer terminal forever
It is interesting to see that after years of finding new ways to interface with computers, professionals always end up on the terminal. Why the terminal of all things?
Read more: https://janikvonrotz.ch/2026/08/17/computer-terminal-forever/
Terrific article from the very helpful Adrien (aka statox) about how he made a little #Vim plugin to highlight the text that you just yanked:
https://www.statox.fr/posts/2020/07/vim_flash_yanked_text/
I'm posting partly because it's a neat idea, but mainly because it highlights one of my favourite things about Vim: how easy Vim makes it to knock up little bits of customization.
Go sharpen your saw!
“Vim has a one-tier system: the user can do anything a plugin can. Everybody is always able to extend the system and have as much control as they want.”
https://buttondown.com/hillelwayne/archive/vim-wants-you-to-control-vscode-wants-you-to/
I have this #firefox extension called #vimium.
Of course, I'm a #vim nerd and I thinks it's awesome.
But here is why it's also great to have it even if you don't use vim : press `f` and have all the clickable links showed to you.
Looking for this "Continue without accepting" dark pattern ? Here it is. Want to unsubscribe from this list you never subscribed ? Here it is.
"Accessibility" for the ables in those dark ages.
Also : fuck you if you coded those dark patterns.
Alright, before I veer away .....if you are sticking to the age-old stuff like me .....😜
Emacs ---> https://github.com/emacs-tw/awesome-emacs
Vim --> https://vimawesome.com/
A dash of "modern salt" to spice things up ....but very, very limited, just not to bloat it.
Vim: 57 CVEs tracked, avg CVSS 5.1, max 9.2. 52% unpatched, +23 CVEs in 2026. Top weakness: buffer overflow (CWE-122). Even open-source editors need vigilance. #Vim #infosec #cybersecurity
@tuban_muzuru Yeh I asked on #vim and someone there suggested scrollbind - it's good! It would be even better if it could do line diff (ie without clever alignment) - but it does handle those big files easily!
I've always felt that #Vim/#Neovim's dictionary was slow to suggest corrections.
I timed it today and it's indeed between 0.14s and 0.27s. Really noticeable when it's the delay between pressing a key and the UI rendering.
to my shame, i couldn’t quickly find a way to make both auto-pairs and vim-surround properly work with «guillemets» (aka french quotation marks). both are excellent #vim plugins, the problem must be with my limited knowledge and patience, and i’d appreciate some #fedihelp here =/
the problem is not that i can’t add '«':'»' to the auto-pairs’ g:AutoPairs, and re-init the plugin, it’s that it doesn’t work as intended. i don’t remember what went wrong with surround, but it was smth similar, it taking offence at my un-american preferences =(
You’ve been waiting a long time for this. Now it is here.
The home gym for your Vim movement. To get you in better form. And no membership. Ever.
Enough of the mashing. Enough of x, x, x, x, x. This is not editing. This is junk volume.
Neon Vim Gym builds the muscle memory. Real sets. Real targets. When you do too much junk volume, the bar at the bottom of the screen turns red. Like my face after leg day.
And for the serious lifters: make your own workout. Get help from Claude, the fitness trainer. Write your own sets. Load the plan from GitHub. No spotter. No excuses.
Get Vim Fit.
https://sites.google.com/view/paperstackpro/home/games
#vim #neovim #vimtutor #vimfit #editor #terminal #productivity #learnvim #devtools
Vitaminas para Vim: Plugins, resaltado de color y autocompletado #programación #programas #sysadmin #c #plugins #python #vim #vim_plug
https://www.ochobitshacenunbyte.com/2026/08/13/vitaminas-para-vim-plugins-resaltado-de-color-y-autocompletado/
My blog is a compiled artifact, not a rented form. #Indexcards → #Logseq → #Typst → static HTML → #Surge, deployed in seconds. Zero npm bloat, zero subscription, zero platform I don't control. Every post starts on paper before it ever touches a keyboard. That's not aesthetic, that's architecture.
And honestly? I feel bad for Substack writers now. They picked an overrated web-editor over understanding how their own words get published. That's not a tech choice, that's an intellectual shortcut.
You can't claim to be a serious writer while being incurious about the machine that delivers your writing.
Learn your stack. Own your words.
@jtr @ericsfraga I think modal editing in general is ergonomic and it doesn't particularly have to be vim. There's boon (https://github.com/jyp/boon) and meow (https://github.com/meow-edit/meow). Since you've never used vim, I'd recommend these packages instead.
I transitioned to emacs coming from vim so using evil (https://github.com/emacs-evil/evil) was natural to me. A huge drawback of this package is that it hijacks certain emacs bindings but that's also necessary if you want precise vim emulation.
Boon and meow offer modal editing and the benefits in terms of ergonomics without sacrificing emacs keybindings. I'm trying to move to boon but it's hard to let go of evil when I already know vim.
Good luck and I hope your pinky gets better. :)
@rachel it's just sad that neovim (and vim) got enshittfied with SlopCode.
EVi by @mrmasterkeyboard supports Lua like neovim.Personally I just use ne because it's a good CLI alternative to proprietary editors like Sublime Text…
#neovim #vim #Enshittification #SlopCode #AIslop #Lua #editor #IDE #plugins #ne #evi #Editors #AI #slop
@mrmasterkeyboard @rachel yeah, that's what I've seen so far.
VimScript and a clean and simple, deshittified vim fork…Stuff like Lua support and plugins are obviously in the 'We have time and spoons to extend and add features' drawer of the 'ideas not decided upon' shelf inside the 'nice to have' closet…
#FLOSS #commentary #NiceToHave #evi #vim #neovim #lua #NiceToHave
Now it needs to percolate through to the quarterly package repo, which'll take another month and a half, but at least that doesn't need any manual intervention.
For years I ran a Python Pelican / Markdown / Bootstrap 4 stack. It worked, but compiling slowed down around ~200 entries, and maintaining Python + JS code ate more time than the writing itself.
So I rebuilt the whole blog. Notes start life in a Logseq/Obsidian knowledge graph, mirroring the node/card structure of a physical notebook; an idea progresses from a numbered card straight into a .typ file. Typst compiles that file directly to HTML, genuinely fast even at scale.
A small Node.js script (no extra npm) reads the compiled metadata and assembles a timeline grouped by ISO week number.
The result: Vim stays at the center of my blog editing, while the rest of the stack: Typst, the plugin, the build script, just gets out of the way and scales with it.
There's a read-it-later button at the top, you can set a reminder in your calendar in case now isn't the right moment.
#PKM #Obsidian #Logseq #Vim9Script #Neovim #Vim #Typst #Zettelkasten
https://paperstackpro.surge.sh/2026W33_typst-vim9script-a-journey-to-a-new-self-published-blog.html
Découverte Neovim : le folding natif. `zM` et tout un fichier Rust se replie — il ne reste que les signatures. `zR` et tout revient.
Naviguer dans des centaines de lignes devient enfin lisible.
Bonus : un pli fermé compte comme une seule ligne, donc `dd` sur une fonction repliée la déplace en entier.
Finally found time to migrate to full vim9script. Rewrote my vimrc in vim9script and built a lightweight plugin manager that leverages packadd—no external dependencies, just pure VimScript.
Running 100% native PowerShell on Windows. The new colorscheme ties it all together beautifully. Setup feels snappy and clean. Super happy with how this turned out.
Exercices quotidiens sur nvim. Aujourd'hui : les modifications.
Je repasse en revue toutes les commandes du chapitre : i a I A o O pour
l'insertion, les opérateurs d, c et y, leur version ligne entière dd, cc,
yy, les majuscules D, C et Y, le collage p et P, les corrections d'un
caractère x, s et r, l'indentation >> << == gg=G, l'incrémentation avec
Ctrl-a et Ctrl-x, et la répétition avec le point.
Du connu pour l'essentiel. Mais deux choses qui vont bien m'aider.
J, qui joint la ligne suivante à la ligne courante.
La seconde, c'est une question de portée. Je savais qu'un opérateur se
combine à un déplacement : dw supprime jusqu'au mot suivant, d$ jusqu'à la
fin de la ligne, dG jusqu'à la fin du fichier, d} jusqu'au paragraphe
suivant. Ce que je n'avais pas mesuré, c'est jusqu'où ça va. f, t et /
sont des déplacements comme les autres, donc des cibles comme les autres.
df; supprime jusqu'au point-virgule, celui-ci compris. dt; s'arrête juste
avant. d/erreur supprime jusqu'à la prochaine occurrence du mot "erreur".
J'utilise f, t et / tous les jours pour me déplacer et pour chercher. Il ne
m'était jamais venu à l'esprit de m'en servir comme cible d'une
suppression, d'un changement ou d'une copie. La même touche sert deux fois.
Je progresse 😅
Sooo, I looked into how you can pass line and column numbers to different text editors. How did you spend your evening? 😅
https://www.zyzzyxdonta.net/posts/pass-line-number-to-editor/
#Blogging #IndieWeb #SmallWeb #Wikidata #TextEditor #Vim #Emacs