vim

I think I'll give #vi a go on my #OpenBSD desktop instead of using #vim for a while and see how I get on. Got my config in ~/.config/vi/exrc and I'm learning new to me stuff so all is good.

I've still not given up on #Vi as my editor instead of #Vim and to be perfectly honest, I'm not really missing the fancy Gruvbox theme and Vim's auto-completion. It's making me learn new tricks and stops me relying on the help of plugins. Good for the old grey stuff I'd say! I even changed the 88x31 button on my websites footer from Vim to Vi. #RunBSD #OpenBSD

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

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

I just spent a half-hour hacking in the #Neovide (GUI version of #neovim) #Lua config file, and I have figured out abbreviations and custom keymapping, which means I can move my "production" editing from #gVim to Neovide with a clean Lua config file.

Do I need to move away from gVim/#Vim? I'm not sure, but we're in this game to try new things, right?

Is it worth it to move from Vimscript to Lua?

Whoah ! My #OpenBSD #vi config is a hearty 10 lines long compared with the 260 of my minimal #vim config. Yeah I know I don't have theme support and what not but I'm prepared to give this a shot without all the fancy bells and whistles. The only thing it doesn't do is display my icon fonts in scripts but it's made me wonder if I even need them now. Yes nvi2 will display them but it feels like cheating to install that when n(vi) is in the base on OpenBSD.

EDIT OK thanks to @r1w1s1 I'm now at 39 lines long. 🤣

OH so it looks like the new #Vim fork #Evi is looking to drop vim9script.

Feature freezing vimscript and implementing Kuroko scripting?

https://codeberg.org/NerdNextDoor/evi/issues/46

That's a no from me then. Think I'll just be sticking to what I know which is Vim.

Currently I'm a #vim user with only two plugins loaded by vims own system no packer or anything. They are the gruvbox theme and colorizer to color HTML color codes.
I've been researching to see if I could work with #nvi and wondered about undo history and found that it might be possible ?

u

Undo the last change made to the file.
If repeated the u command alternates between these two states.
The . command when used immediately after u causes the change log to be rolled forward or backward depending on the action of the u command.

If you're an nvi user what other tips or hacks are there that I should know about ? I don't suppose there is some magical way to theme it ?

Haha just resolved a couple of niggling bugs in my blogs html using n(vi) on #OpenBSD . I know it's not much but I used to use vim before and I'm easily pleased. I wonder if you get a logo like this one that says #vi instead of #vim ???

The nvim-treesitter repository was archived via @rwdf https://lobste.rs/s/jr4acs #editors #programming #vim
https://github.com/nvim-treesitter/nvim-treesitter

haunt.nvim: Ghost text bookmarks for Neovim https://lobste.rs/s/5ghcmr #vim
https://github.com/TheNoeTrevino/haunt.nvim

Trying out #nvi-1.81.6 on #Debian as my primary editor on my work box for a bit.

At first, I was sad that I could no longer

some_command |vi

like you can with (neo)?vim, but then I realized you could just as easily

vi <(some_command)

Hmmm, the lack of line selection mode is a bummer. This might have more pain points than I was anticipating. XD

Maybe I should try #vim-tiny?

Vim Classic 8.3 released https://lobste.rs/s/6xwqvv #editors #release #vim
https://vim-classic.org/news/vim-8.3-released.html

Drew Devault has just updated his #Vim fork, “Vim Classic”, now in version 8.3.

Like Vim, but without the compatibility-breaking VimScript9, and without any AI-generated code. A sane maintenance process. This is the legacy Vim deserves.

https://vim-classic.org/news/vim-8.3-released.html

Vim Classic 8.3.0 is released 🎉

https://vim-classic.org/news/vim-8.3-released.html

This is the first release of #Vim Classic, a 100% human-written fork of Vim. Happy editing!

New #blog #post: Vim Carnival Entry: "The Motion that Changed Everything."

https://rldane.space/vim-carnival-entry-the-motion-that-changed-everything.html

1224 words

cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn

(I will happily add/remove you from the chorus upon request! :)

Thanks to @hyde for the blog concept, and immediate apologies if you get trapped in a #hellthread! 😄

#rlDaneWriting #blost #vi #vim #nvi #editor #VimCarnival #TheMotionThatChangedEverything #modal #ADHD

I published a DRAFT of “My TiddlyWiki Customizations⁠ ⁠⛮ (Vim key bindings, journaling, and more)”
https://www.ii.com/customize-tiddlywiki/
As always, feedback is welcome! I'm very much a #TiddlyWiki and #TiddlyDesktop #newbie
#InfiniteInk
#Journaling #NoteTaking #Wiki
#Productivity #GTD #Tech #GVim #Vim #WebDev #Words #Writing #Byℵ #ByNM

I have like zero respect left for developers who use LLMs to write or maintain their software.

I don't even care for the reasons why they use this unethical piece of... technology.

Technology trained on data they don't own. Technology owned and shaped by fascists. Technology that sends its crawlers around the globe to suck every bit they can find to dump their models into big f***ing corp data centers. Data centers that are polluting the air with their big ass gas plants.

But hey! "Leave ethics aside". "That's how software development works today!".

I'm so sick of this and about everyone supporting this industry.

If you feel targeted, you are welcome. I have zero respect for you or your software garbage. I just wish you the worst.

#AI #LLM #FLOSS #Linux #vim #gohugo #FOSS #FckAI

eh: a minimalist vi-like editor https://lobste.rs/s/au6oho #editors #unix #vim
https://codeberg.org/SirWumpus/eh

Good Tools Are Invisible https://lobste.rs/s/ydjxee #editors #practices #vim
https://www.gingerbill.org/article/2026/07/10/good-tools-are-invisible/

God, what a fucking asshole.

Anyways, I've already spent some time removing #neovim from about half of my build/development containers. For now I'm going back to #vim, but once vim-classic or #evi is packaged in #debian, I'll switch to one of those.

Yay! Thanks to Bruce Simpson, my vim-classic, the non-slop fork of vim, port for #FreeBSD is now merged.

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.

https://www.freshports.org/editors/vim-classic/

#VimClassic #vim

ICCF Holland Annual accounts 2024 https://lobste.rs/s/sd9ypu #pdf #vim
https://iccf-holland.org/jaarrekening2024_EN.pdf

Oyez Oyez !

Vimistes, NeoVimistes, voir même Vistes ou EVistes ? Emacsists, Nanoïstes, Edistes...

À #Grenoble, le mardi 27 octobre à 19h à #LaTrubineCoop se tiendra un évènement de renom : un #TupperVim https://tuppervim.org/ !

Ne préparez rien, venez avec un truc à qui miam ou qui glou et pointez vous au bon endroit https://www.openstreetmap.org/node/2782756987#map=19/45.184322/5.721137 à la bonne heure.

#vi #vim #nvim #neovim #evim