#Vim

Episode 26 of our technology podcast @RuntimeArguments (http://RuntimeArguments.fm) — and it's our one-year anniversary! This one's called "Why You'll Never Switch Editors (And What You're Missing)".

Wolf @YesJustWolf surveys the text editor landscape — Vim, Emacs, VS Code, Helix, and some new AI-powered contenders — while Jim @jammcq defends his 42-year Vim habit (and gets talked into looking at TreeSitter and LSPs).

As always, we want to know what you think:

feedback@RuntimeArguments.fm

https://www.buzzsprout.com/2469780/episodes/19034506

#TextEditors #Vim #NeoVim #Emacs #VSCode #HelixEditor #LSP #TreeSitter #AICoding #Podcast #TechPodcast

Last week, something broke in #vim
Ctrl+PgUp used to switch to previous tab, Ctrl+PgDn to the next tab.
Since last week, both only work in GVIM. In a terminal, Ctrl+PgUp moves the screen one line down instead. Ctrl+PgDn works as expected. Any ideas anyone?

I saw that there are some ports of vim for the Commodore Amiga... Any weird old retro computers with ports of Emacs out there?

It would be funny to set up an old-ass computer in my work office and do all my work there ;P

#vim #emacs #retro #computing

Stolen from the nerdiscord.

#Vim #Neovim #Quacken #Ergol #QwertyLafayette

Alt...

Screenshot on a DC anime. — Superman, holding a mug of hot coffee: “so, you aren’t using AI” — Batman replies: “I’m not even using a mouse”

Je découvre l'utilisation de Quickfix (il était temps, je crois !) avec mon LazyVim :
- <Leader>sb (pour chercher dans le buffer actuel)
- Je tape la chaîne recherchée et j'obtiens toutes les lignes comportant celle-ci
- CTRL-Q : Ouvre la liste obtenue dans une fenêtre Quickfix (et là je peux soit naviguer, soit copier/coller cette liste pour en faire ce que je souhaite).

Note: Nvim Quickfix
https://shaarli.demapage.fr/shaare/Kx0eSg

#NeoVim #Vim #Shaarli2Mastodon

What are your thoughts on Helix, especially when coming from Vim?

https://helix-editor.com/

#HelixEditor #Vim

For anyone interested, I updated my #neovim config for 0.12.
But I also wrote about it. The why, the how. It's targeted at people with some experience with either #vim or #nvim who use some off-the-shelf distros but want to dive into the DIY configs.

https://gitlab.com/pcoves/nvim#story-time

Feel free to tell me if I'm missing something. It's hard to know where to put the limits.

#Fediverse people taking #notes with #Vim / #neovim would you be interested to share your experience ? ⤴️

#blog #writing #plaintext #mastodon

[lien] What happened to nvim-treesitter.... Why did it get archived? 😶 : r/neovim #nenousfâchonspas #gik #vim

#Vim carnival this month with the following topic: How do you use Neovim/Vim to build your knowledge management?

If you are interested, send me a link to your #blog post. I will collect all of them until the end of the month.

#FLOSS #FOSS #Neovim #editor #terminal #shell #opensource #Pkm #notes #plaintext #writing #blogging #bloggers #indieweb #carnival #journaling

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

Stop editing at 10% of Vim's power. Master registers, :norm, fuzzy completion, linematch diff, and 16 more Vim tips and tricks. Tested on latest Vim 9.2.

Full guide here: https://ostechnix.com/vim-tricks/

#Vim #Vimtips #Vimtricks #Editor #Opensource #Linux

#Claude trouve une faille dans #Vim et #Emacs. Il a dit à Claude Code « il paraît qu'il y a une 0-day dans Vim. Trouve là ». Et Claude a sorti une faille réelle et inconnue jusqu'alors.
https://linuxfr.org/users/faya/journaux/claude-trouve-une-faille-dans-vim-et-emacs
#ia

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

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.

A eulogy for Vim @ddevault
https://drewdevault.com/2026/03/25/2026-03-25-Forking-vim.html

“I don’t think it’s cute that someone vibe coded “battleship” in VimScript. I think it’s more important that we stop collectively pretending that we don’t understand how awful all of this is. I don’t want to use software which has slop in it.”

“In short, I invite you to use Vim Classic, if you feel the same way as me, and to maintain it with me, contributing the patches you need to support your own use cases.”

#Vim

Drew DeVault writes about the Vim situation re: AI slop infection, and he decided to make a long-term maintenance fork of Vim 8.x which is a very welcome alternative to any faster-moving forks that should appear.

As always, he also found the right words for the situation in general: https://drewdevault.com/2026/03/25/2026-03-25-Forking-vim.html

#vim #foss #floss #noai #antiai

@elena

Perfect setup ... You only missed #neovim / #vim 😅

@ilja @stefano @teapot_ben @drfyzziks @antoine_ali @stereo @jan

@atoponce I solved this by keeping `:sp` and `:vsp` which make sense to me in #vim and by using `<prefix>-` and `<prefix>|` in #tmux. `-` and `|` are visually explicit. See my config if it helps : https://gitlab.com/pcoves/tmux/-/blob/master/tmux.conf?ref_type=heads#L11-12

Because of slop concern, @drewdevault is forking Vim to make Vim-classic with the laudable goal of "not changing anything"

https://drewdevault.com/2026/03/25/2026-03-25-Forking-vim.html

What’s funny is that I’m, at the same time, toying with "vis", which is Vim without a lot of things I don’t use (tabs, file browsing, network, GUIs…).

https://www.brain-dump.org/projects/vis/

In the removed list, the only thing I use heavily is EX mode. So I must investigate how they replace it.

#vim #neovim

In #tmux, a "horizontal split" pane window places the panes side-by-side via "Ctrl+b %" or ":split-window -h".

In #Vim, it's a "vertical split" by executing either "Ctrl+w Ctrl+v" or ":vsplit".

No wonder I'm always confused.

Is it a horizontal split because the windows/panes or horizontally placed, or a vertical split because there is a vertical line separating the windows/panes?

#Linux

Alt...

Screenshot of Konsole showing a split pane layout of two panes side-by-side. Pane 0 is on the left, pane 1 on the right.

Alt...

Screenshot of Vim showing two editing windows side-by-side.

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?

Not gonna lie, a few years ago when I eared @robinm asking for a built-in plugin manager in #vim / #nvim, I was not convinced.

Why? Because I thought it was already the case. `pack/{opt,start}` has been around for quite a while now and I used #git #submodules to have a portable configuration.

Since then, I've used various plugins manager. They're handy but don't offer much more than the built-in.

And now, back to sugar-coated basics: https://echasnovski.com/blog/2026-03-13-a-guide-to-vim-pack.

I now agree with @robinm.

hey, #EVi reached 100 stars on #Codeberg!!!

https://codeberg.org/NerdNextDoor/evi

#Tech #Technology #Vi #VIm

Alt...

The EVi repo page on Codeberg, showing 100 stars reached.

Because of editor developer shenanigans, I all of a sudden gathered spoons to try the Helix editor. And boy, howdy, going back to an editor that only works in the command line has opened an interesting yak shaving expedition.

Ya see, I've been using GUI IDEs/editors since before neovim was a thing, when I lost the energy to mess with my vim config after it broke, I went to vscode with a vim keybinding addon and stayed there because it was good enough, and it had become the place where extensions appeared first. So there I stayed, until vscode became too aggressive with its AI stuff, and I decided to check out zed. Granted, zed also had AI functionality but it had a kill switch that made it all disappear. Zed was amazingly fast, and made switching from vscode super easy, and I was happier.

Then the last few weeks happened; Zed's updated their weird terms of service to be weirder, (which I never agreed to because I installed the arch package), and vim had the most embarrassing slop PR conversations one could think of.

So, I felt the sudden urge to change the main tool of my trade once again, and no dear reader, unlike some people, I don't consider the slop machine a tool of my trade.

So I looked at neovim, which sadly triggered the claude block warning, but didn't seem as brainwormed as vim yet. I heard about gram, which was an unfucked version of zed, but when I looked at it, wasn't properly packaged for my setup. Then I also looked at helix, which some people have said good things about, especially about its different take on modal editing, and it didn't have any obvious signs of slop at all.

As I had the spoons, I decided to try this helix thingamajig for a week, and see how it would mess up my muscle memory, which has been abused by vi(m)-style keybindings since the 90s.

This is all a long winded way to say that I am now back on a pure terminal-based development setup and... wow this stuff improved.

I discovered Zellij, which redefined what I thought of as a terminal multiplexer. I've used tmux for a long time, and screen before that, but Zellij makes its panes feel like discrete windows when it comes to selecting text and mouse controls.

Helix is very interesting, it sure is messing up my muscle memory, but it sure feels like it might be worth it, as some more complex stuff feels more logical than it ever did in vim. And because of the language server protocol, it does all the rust/go/etc operations just as good as zed or vscode did, better even, as I find the UI calmer and less surprising than I did in those GUI editors.

I've also been playing with lazygit and yazi, although not as much, as I've always used bash/zsh/fish for git and file management, so my need for those isn't too great. And then there's a whole lot of other small modern CLI tools that make life better, like fd, replacing find, sd replacing sed, and more.

The point of this long, barely coherent rant is to get off my chest just how much nicer terminal based development has become since last I gave it a proper go, and that if you haven't looked at this in a long time, or even ever, it might be worth a try.

#Terminal #CLI #HelixEditor #Helix #Zed #tmux #Zellij #VSCode #SoftwareDevelopment #vim #neovim

I also aliased #Vi and #VIm to #EVi on my MacBook and HP laptops.

EVi will be my main terminal text editor from now on.

https://codeberg.org/NerdNextDoor/evi

#Tech #Technology #FuckAI

#EVi is now on irc.oftc.net! Come out hang out at the 'evi' channel!

I also plan Matrix and Fluxer later on!

#VIm #Vi #Tech #Technology #IRC #FuckAI

News! #EVi is set to appear in @the 's #NoAI list in their April update!

https://forge.starlightnet.work/Team/No-AI/commit/74c2c286497b10d561141c6335423f263e97fed0

#Vi #VIm #FuckAI #Tech #Technology

“A Guide to vim.pack (Neovim built-in plugin manager)”
“A somewhat concise yet comprehensive guide to vim.pack: how it works and how to use it.”
https://echasnovski.com/blog/2026-03-13-a-guide-to-vim-pack

#Vim #Neovim #Lua

[lien] Emacs and Vim in the Age of AI - Lobsters (batsov.com via hongminhee) #gik #vim #ai

Emacs and Vim in the Age of AI

https://batsov.com/articles/2026/03/09/emacs-and-vim-in-the-age-of-ai/

#HackerNews #Emacs #Vim #AI #Productivity #Coding #Tech

https://codeberg.org/NerdNextDoor/evi

@soller

Just the other day I was barked at and blocked, in the context of the #vim "controversy"
For saying that if you insist on #Ai #vibecode free purity...
...you will be using a clay tablet for your computing needs soon.
And here we are.

I'm looking forward to a HomoSapiensLinux fork where every line of code is chiseled from a pure human bone with tools forged in artisan smithy...
...that's going to collapse in controversy because major contributors will be sprung vibecoding 😄

BTW: Any of you read that .md file before conniptions?
Would be good idea to get some human #codemonkeys to comply with the directives there 😁

I've been scouring the web for peoples opinion on #EVi and I'm seeing a lot of unfair assumptions and judgement for a project forked 3 days ago.

Don't mind if I vent for a second? Please read.

🧵

#Tech #Technology #Vi #VIm

https://codeberg.org/NerdNextDoor/evi

#evi #vim #ai #opensource

EVi, a hard-fork of Vim v9.1.0 (Jan 2024)
https://codeberg.org/NerdNextDoor/evi

#vim #noai

VIM

Bram Molenaar

human programming

Background

It has come to my attention that my beloved VIM has become invested with LLM AI slop

The lead programmer is not following standard rules of coding anymore.

People have called him many things, but one thing is certain. The man is intelligent in the programming field and knows what he wants.

VIM needs LLM slop!

the programmer screams!

We don't think so!

we roar back!!!

A couple of programmers decided to create a hard fork of vim

VIM

• version V9.1.0 January 2K24
• last commit
• no LLM slop
• Pure Bram Molenaar level human crafted code

If you are categorically against large language model slop this is a project for you to support!

This is a hard Fork meaning that you cannot merge it back with me VIM main source line

Project

https://codeberg.org/NerdNextDoor/vim

Source
https://mastodon.social/@mrmasterkeyboard/116192873098653079

https://codeberg.org/NerdNextDoor/vim

#VIM #VIMMasterRace #programming #LLM #AI #hostile #environment #Amiga #BSD #freeBSD #netBSD #openBSD #ghostBSD #LINUX #mac #win64 #OpenSource #POSIX #technology #mathemathics #physics

[lien] EVi, a Hard-Fork of Vim - Hacker News #nenousfâchonspas #gik #vim #ai

@umbraroze There's actually little to no benefit in this, unless you have an affinity for Lua.

#vim #neovim

EDIT 2: I forgot to update this, the project is called EVi now.

EDIT: I updated the fork to last commit before the AI slop. It's now relatively new.

hard-forked vim at release 9.1.0 (Jan 2024)

https://codeberg.org/NerdNextDoor/vim

maybe we can get a group of people behind this??

Fuck AI.

#VIm #FuckAI #Tech #Technology

self-report - take 2

preivously: https://analognowhere.com/_/ratmrg/

#unix_surrealism #technomage #comic #vim #openbsd #linux

Alt...

Fish: "So, this is everyone who thinks you're cool for using vi over vim." There's a million penguins around.

Every now and then, a little light shines in and reminds me that I'm not the last person on earth who finds the slop machines concerning.

https://codeberg.org/NerdNextDoor/evi

This project is both hope, a solution to a growing problem, and a way forward.

I'm hoping it picks up momentum quickly.

#StopSlop #noAI #vim

Made a pull request to small-hack/open-slopware to add #VIm to the list.

https://codeberg.org/small-hack/open-slopware/pulls/38/files

#Codeberg #FuckAI

EDIT: I updated the fork to last commit before the AI slop. It's now relatively new.

hard-forked vim at release 9.1.0 (Jan 2024)

https://codeberg.org/NerdNextDoor/vim

maybe we can get a group of people behind this??

Fuck AI.

#VIm #FuckAI #Tech #Technology

@RussSharek @AndrewRadev

As a VIM user since the Amiga, I will research this to the bottom

Thank you for your toot which brought this important subject to my attention

#VIM #VimMasterRace #opensource #Linux #Amiga #Technology #posix #mathematics #Physics #chemistry #Linear #Algebra

Now that #vim seems to be going down the #AIslop drain... might this finally be the year of #Emacs on the #desktop?

Also containing *proper" #AI since the #80ies!

Re: https://hachyderm.io/@AndrewRadev/116175986749599825

#GNU #Unix #Eliza #EditorWars

Alt...

A terminal running Emacs, running Eliza, the Emacs psychiatrist.

fuck fuck fuck fuck fuck fuck fuck https://mastodon.social/@normalmode/116176453948316197 #vim

I had been meaning to gently consider neovim sometime…how’s the slop quotient over there? 😒

After decades of #vim and #neovim usage, I finally used the _void_ register instinctively.
One day, I'll grok #vi, one day.

Tabs vs spaces has always been a controversial topic. Thankfully, #vim isn't biased in any way.

To convert spaces to tabs, use `:set noexpandtab`, then `:retab!`.

Convert tabs to spaces with:

:set expandtab
:set tabstop=4
:set shiftwidth=4
:retab

New post: Neovim Crash Course for Sysadmins

Not a beginner's guide. This covers the things you still get wrong after years of Vim - efficient navigation, why your paste lands in the wrong place (and the one-key fix), YAML indentation workflows, quick macros, and what Neovim's LSP actually gives you for infrastructure work.

Written for people who edit configs and playbooks all day.

https://blog.hofstede.it/neovim-crash-course-for-sysadmins-the-20-that-solve-80-of-the-pain/

#neovim #vim #sysadmin #devops #linux #ansible #yaml

[lien] AI Completion | AstroNvim Documentation #gik #vim #cli #ai

Until this is resolved, I'll be using console Vim, which does ship with Bluefin Stable.

I generally prefer gVim because I use the system clipboard a lot, and it's slightly easier with a GUI app. I also use the mouse a bit. That's the kind of Vimmer I am.

I can make it work with console #Vim, and that's probably better for me in the long run.

I would have moved to #Neovim GUI #Neovide, but my .vimrc does not work, and it would be a heavy lift to re-create it.

TIL that #vim can edit files *inside* a zip file. 🤯

Ugh, come on. Is nothing sacred anymore?

(via https://kolektiva.social/@SharpCheddarGoblin/116131579930345384)

#Vim #Neovim #Claude #AI

Alt...

Screenshot from the Neovim repository on GitHub. There's a warning box at the top that says "A user you've blocked has previously contributed to this repository: claude"

Alt...

Same thing, but for Vim's repo.

I’ve been trying to use \n in %s regexes in #vim to replace text with newlines for a loong time, turns out i have to use \r

I'm not #CoryDoctorow, which means my posts have typos (when I forget to turn on #vim's spellchecking features), but also I won't commit #SuicidebyLLM

https://wok.oblomov.eu/tecnologia/suicide-by-llm/

#LLM #genAI #writingTools