#editorwar — Public Fediverse posts

@restorante @ramin_hal9001 @hell @tusharhero

My take(s) on that #Emacs and #vim comparison part:
https://karl-voit.at/2026/01/23/Emacs-vs-vim-Cargo-Folding-Bike/
and https://karl-voit.at/2015/10/23/Emacs-is-not-just-an-editor/

#publicvoit #editorwar #editorwars

@restorante @ramin_hal9001 @hell @tusharhero

My take(s) on that #Emacs and #vim comparison part:
https://karl-voit.at/2026/01/23/Emacs-vs-vim-Cargo-Folding-Bike/
and https://karl-voit.at/2015/10/23/Emacs-is-not-just-an-editor/

#publicvoit #editorwar #editorwars

@tusharhero thanks for the shout-out!

“people who have gone from neo/VI/m to Emacs or wise verse - what made you swap? what made you then either stay or revert?”

@hell the article mentioned by Tusharhero is a little long, so to summarize it in a way that more directly answers your question: I basically realized that Emacs was not a text editor, it was a programming language designed for text editing that came with a built-in text editor and IDE. And the built-in editor and IDE are setup so that you don’t really need to learn the Emacs Lisp programming language to use it.

I had become frustrated with my editor (Vim) my terminal multiplexer (Screen or TMux), my shell (Bash), and many of my other CLI tools all being programmed, scripted, and/or configured in different languages. For example, when trying to get my shell to notify my editor that a build process completed, I was able to program Vim and my shell scripts to both use inotify or similar tools to do so, but I just thought it was a little ridiculous that I had to hack together solutions to these problems.

So I started thinking about ways of using the CLI with just one programming language and one runtime. Then it hit me: Emacs is exactly that: a combination of Tmux, Vim, Bash, and dozens of other tools all programmed in Lisp. Once I realized that, I decided I didn’t care how hard it was to use, it was exactly the tool I needed so I had better just learn how to use it. And it turned out not to be too hard anyways.

The best part was, I hardly ever need to write my own tools anymore because I was always able to find some Emacs Lisp code somewhere that solved practically any problem I had ever come across.

If you’d like to know more, then yeah, read my article, or ask me anything you’d like here on the fediverse!

#editorwar #editorwars #vi #vim #neovim #emacs

@tusharhero thanks for the shout-out!

“people who have gone from neo/VI/m to Emacs or wise verse - what made you swap? what made you then either stay or revert?”

@hell the article mentioned by Tusharhero is a little long, so to summarize it in a way that more directly answers your question: I basically realized that Emacs was not a text editor, it was a programming language designed for text editing that came with a built-in text editor and IDE. And the built-in editor and IDE are setup so that you don’t really need to learn the Emacs Lisp programming language to use it.

I had become frustrated with my editor (Vim) my terminal multiplexer (Screen or TMux), my shell (Bash), and many of my other CLI tools all being programmed, scripted, and/or configured in different languages. For example, when trying to get my shell to notify my editor that a build process completed, I was able to program Vim and my shell scripts to both use inotify or similar tools to do so, but I just thought it was a little ridiculous that I had to hack together solutions to these problems.

So I started thinking about ways of using the CLI with just one programming language and one runtime. Then it hit me: Emacs is exactly that: a combination of Tmux, Vim, Bash, and dozens of other tools all programmed in Lisp. Once I realized that, I decided I didn’t care how hard it was to use, it was exactly the tool I needed so I had better just learn how to use it. And it turned out not to be too hard anyways.

The best part was, I hardly ever need to write my own tools anymore because I was always able to find some Emacs Lisp code somewhere that solved practically any problem I had ever come across.

If you’d like to know more, then yeah, read my article, or ask me anything you’d like here on the fediverse!

#editorwar #editorwars #vi #vim #neovim #emacs

@jpmens @ed1conf ed needs an add-on such as mountpoint-s3 [1] to do this. Working on a way to do this using #emacs_tramp, which comes built into #emacs. This may settle the #editorWar s.

[1]: https://github.com/awslabs/mountpoint-s3

#Emacs vs. #vim Real World Analogy: #CargoBike Vs. #FoldingBike
https://karl-voit.at/2026/01/23/Emacs-vs-vim-Cargo-Folding-Bike/

This isn't supposed to deliver fuel to the gratuitous #editorwar.

It's supposed to clear up a few things why the two tools are so fundamentally different.

HTH

#orgmode #editorwars #publicvoit

#Emacs vs. #vim Real World Analogy: #CargoBike Vs. #FoldingBike
https://karl-voit.at/2026/01/23/Emacs-vs-vim-Cargo-Folding-Bike/

This isn't supposed to deliver fuel to the gratuitous #editorwar.

It's supposed to clear up a few things why the two tools are so fundamentally different.

HTH

#orgmode #editorwars #publicvoit

#YouTube #AI gets automatic key concept identification wrong:

I'm about to watch a video about two project interaction libraries for my favorite #TextEditor (#Emacs). They're called #Projectile and project.el.

Below the video, YouTube shows an image of a missile, under a heading that says "Key Concepts". Below the image, it says: "A projectile is an object that is propelled by the application".

The hashtags #OOP and #EditorWar come to my mind.

#YoutubeExperiment

#vim: much more versatile than I thought but still just for wankers. 😈😜

#editorwar #Emacs #fun

#vim: much more versatile than I thought but still just for wankers. 😈😜

#editorwar #Emacs #fun

@ollej The best editor is both!

#EditorWar

@xi I’ve made a vim plugin to help you evaluate the elisp code when you edit your .emacs file with vim.

https://github.com/ollej/vim-emacs

#vim #emacs #EditorWar

@xi I’ve made a vim plugin to help you evaluate the elisp code when you edit your .emacs file with vim.

https://github.com/ollej/vim-emacs

#vim #emacs #EditorWar

You can find an attempt to mimic the #VSCode in #NeoVim. Take a look at NVIM-IDEA [https://github.com/ldelossa/nvim-ide]. But this one will be better - #NvChad [https://github.com/NvChad/NvChad]. Learning #Vim is a good investment of your time. If someone tells you differently, they never finished the Vim tutorial. So don't trust those people. If we are talking about Vim, we must mention #Emacs. Check this beauty #DoomEmacs [https://github.com/doomemacs/doomemacs].
#editorwar #editor #ide #programming #coding

O. Ich musste gerade mal vi benutzen statt Emacs.
Ich wollte Einträge in .emacs.d/places löschen, und Emacs verändert das File genau so wenn es den Verweis auf das File selbst einträgt, dass die Änderungen raus fallen.
🤷🏼
#emacs #vi #editorwar #holywar

@kubikpixel
Pfff, das ist nicht dasselbe...#vim ist unintuitiv, #tut ist gold. Basta! Fertich! 😅
#editorwar und so...weisste.... 😉
Aber #tut ist echt so eine Erleichterung fuer schwache Systeme wie meins hier. Macht richtig SPass zu benutzen.

@sum
:)
Don't need no raw nCurse on a vhIM or any emacs in the back.
When granddadd-Eee-Dee's got me covered, line by line, cooked.
#ed #editorwar

@stsquad

> those that have not already discovered the delights of #orgmode are destined to recreate it

Except that inserting orgmode time stamps with the current time requires an arcane series of keypresses (two prefix arguments (not sure what that means?) plus `<C-c>` followed by `.`

https://orgmode.org/manual/Creating-Timestamps.html#Creating-Timestamps

In contrast, my vim version involves turning on a specific mode, and then pressing enter

Really captures the #vim–#emacs difference! #editorWar :D

@mwlucas @alexbuzzbee @balrogboogie

(also, when writing that last toot, I noticed that the hashtag #ed prompts me to autocomplete to #editorWar. That seems appropriate, somehow.)

It recently came to my attention that #trunk has a thriving #emacs list but no #vim list at all. This is an outrage that cannot be allowed to stand! #editorWar #cultOfVi

(Seriously though @[email protected] could you create a vim trunk list and add me to it?)

(If you're not familiar with Trunk, it's a group of interest-based lists to help new Mastodon users find interesting people to follow: https://communitywiki.org/trunk)