Piero Bosio Social Web Site Personale

#OverUnder 070 with @edphones He shares his thoughts about #Podman, #Ubuntu, the #Cloud, #Thunderbird, and, #Cucumbers. he also replied to @elena's question.And, we got a recommendation for two #books. And, for the first time, one about #vim ... Finally!! #bloggers #bookstodon #book #blog #fediverse #bloggers #mastodon https://lazybea.rs/ovr-070

@tykaynWhat about Atkinson Hyperlegible Mono?

Ever wonder why vi uses hjkl for movement?It's not arbitrary—it's hardware history. The ADM-3A terminal had arrows printed directly on those keys.ESC was also where Tab is now. Vi wasn't designed for ergonomics, it was designed for the keyboard that existed.http://www.slackware.com/~r1w1s1/nvi.html#_curiosities#nvi #vim #vi

@wtfismyip#Emacs devs give it to git?! 🤔🙄

Hmmm decisions decisions. As an #OpenBSD user I usually prefer #vim with just 2 plugins installed my gruvbox theme and colorizer to color html color codes. But I'm wondering if I really need syntax highlighting and theme support ? You can see my rough and I mean rough .kshrc side by side in vim and vi. I do like a splash of color and do enjoy the command completion though so I guess I will tinker with n(vi) further. #vi

Also something else that I have noticed as an #OpenBSD user is that vi and nvi undo functions seem to both work the same ? I mean you can press u in both to undo and then press . to do multiple undos. Yet I thought it was only nvi that had that feature? I'll have to read up more on both to find differences.

@ljwritesI have both Windows (Alt Codes) and Emacs (Unicode) macros stored in my keyboard for Italian accented capital letters (À, È, É, Ì, Ò, Ù), ~ and `Plans are to also add ellipsis and some dashes for both again as well, sooner or later.There's also the GUI+Shift+S for Windows Snipping Tool, the audio (and mic) on/off, Emacs M-w, C-w, C-y and a few more things.

ICYMI - EVi, a hard-fork of Vim v9.1.0 before AI was used in the project. - Codeberg.orghttps://codeberg.org/NerdNextDoor/evi#evi #vim #ai #opensource

@nuintari Ditto

Hey fedi,So, with the news about #vim, I'm considering branching out and trying different editors/toolchains. Thing is, I've got a #vimwiki that keeps my brain running, a second one that manages the massive project that is #thisOldClownHouse and a third that is my website. I'm hopeful that a non-slop fork of vim is in the future, but I can't maintain one, so I'm wanting to learn about my options.I could use recommendations of things to explore. Optimally tools where the maintainers have stated a policy of not accepting slop, but I'm willing to risk things where we don't have *known* slop being introduced by maintainers.I don't need an all-in-one solution necessarily, but I do need both a text editor and a wiki solution. There needs to be some tooling from which I can render a basic static site from the wiki format. I can shell script just enough to ease the practice of pushing files through a series of tools, but I typically need some handholding, so I'd prefer something that's already pretty well established. I'm not currently looking to leave the terminal, no shade to gui's, just not what I'm looking for right now. edit: Oh, and I'm on #openBSD, so preferably something that's already in ports, but I'd still like to know about small projects too.#askfedi #textEditorAlternatives #noAI

@Rose @lu_leipzig maybe I should make a NyaVi mode…

@mdhughes FYI, it’s spelled “vi”.HTH✌️

@SharpCheddarGoblin Dammit²

FFF.nvimFinally a smart fuzzy file picker for neovim.FFF stands for freakin fast fuzzy file finder (pick 3) and it is an opinionated fuzzy file picker for neovim. Just for files, but we'll try to solve file picking completely.It comes with a dedicated rust backend runtime that keep tracks of the file index, your file access and modifications, git status, and provides a comprehensive typo-resistant fuzzy search experiencehttps://monodes.com/predaelli/2026/02/19/15091/#vim

Configuring #Vim as a Writing Toolhttps://itsfoss.com/news/configuring-vim-writing/