Last week I purged all my IDEs and moved to VIM.

My experience so far:
It is a perfectly viable IDE replacement if you are willing to invest some time to configure it to your needs!

· · Web · 3 · 0 · 5

@Ghosty Also, once you've learned to configure it, reconfiguring on the fly becomes painless.

And just in case you haven't used it yet - open an existing file, start typing, and then do a


That little shortcut's saved me a lot of time.

Why do people keep perpetuating this lie! Vim is just about as relevant as vinyl records, only hipsters care.

@yisraeldov I want to use vim to cut down the GUI programs I have :). Running most stuff inside a console is just more comfortable and cuts down my dependencies.

Vim is also more minimal than VSCodium while having the same functionality if configured properly.

Is this a serious question? I was told not to feed the trolls.

Vim needed to be destroyed. It is not a sane default editor. And there is nothing you can do with vim that you can't do with emacs.

@yisraeldov @Ghosty I must ask, are you serious? Because if it's sarcasm, it's not really funny.

@hund @yisraeldov @Ghosty while I disagree with the extreme option, it was documented to a point how bad vim was. vim means vi improved, yet, plugins disrupt vim too greatly. I can recall times where plugins with missing or incompatible application backends corrupted vim resulting in repeating crashes, freezes and loss of data entry. Vim plugins have no barrier like emacs or mcedit. It will gladly run malware.

For years, BSD pushed vi and nvi, even though vim was there. Emacs never changed.

@hund @yisraeldov @Ghosty meanwhile, ^h ^p in emacs. Emacs has lots of help in it. I should have picked it up years ago. But it was too heavy for my computers up to 2010.

I am exaggerating to get an emotional response, not the same as sarcasm.

Vim is not a sane default editor because it is completely foreign to the way that you edit text in almost all shells (like bash), REPLs, and most other gnu utilities. What is worse is that it is not "discoverable".

The default text editor is something that gets run implicitly, it should not deviate extremely from the environment where it is invoked @Ghosty
@nergal - 1/2

(usually bash). At the very least, it should give some hints about how to use it.

@nergal @hund - 2/2

@yisraeldov @nergal @hund I get what you mean. But I didn’t use vim because it was the default I choose it because I wanted to :D.
I don’t use nano because it has not enough functionality to be used as an IDE replacement.
So I can choose between emacs and (neo-)vim basically. I choose neovim over emacs because emacs has a lot of stuff that I don’t need. Not saying that neovim is perfect out of the box. But neovim is really extensible :).

@yisraeldov @Ghosty @nergal Just because you can't use a piece of software doesn't make it bad.

@hund @Ghosty @nergal The argument wasn't that it is bad, but that it is a bad default editor.

Admittedly, I have very little experience with VIM, tried to learn it once, cause I kept getting thrown into it. I found it to be so counter intuitive and offers no benefit over emacs, so why bother.

OK! Vim is at version 8.x! Plugins can now run native. That is great news! I still do not have a proper vimrc, though. How are your .vimrc?

With emacs, the config starts basic and one may adjust everything after, using various interfaces within the editor.

My problem is remembering the options for help! ^h k gets help for what keys do. ^h m tells what the present mode does. ^h t offers training. There is help for everything! It is to find it.
@yisraeldov @hund @Ghosty

@nergal @yisraeldov @hund My vimrc is a mess :P.

I just change the config file when I feel the need to add/remove/change something. So the Same approach you described with emacs :)

No, it's not the same as emacs because there is an interface to show you what options are available.
@nergal @hund

@yisraeldov @nergal @hund I wasn't talking about that. I was talking about: "[...]the config starts basic and one may adjust everything after[...]

@Ghosty @yisraeldov @hund still, there is no interface to configure. Nothing like a vipw||vigr. There is that deficiency. So, would we agree on that point?

@nergal @yisraeldov @hund I would say that emacs and vim tackle vastly different areas. Vim tackles the area where there is already some kind of workflow setup.

Emacs on the other hand provides a whole workflow package. That's why naming emacs a text editor is an understatement if you ask me :).

Show more

@yisraeldov If you want me to become emotional you have to attack different spots ;). Its just a text editor. The choice of programs is a mixture of rational and irrational decisions. Rational as in the person has thought about what they need and which programs fits those needs best and Irrational as in flavor because that’s just how it is in the end (at least for me :D).
@hund @nergal

@yisraeldov @Ghosty You need to be a bit more obvious when you use sarcasm via text. :)

@Ghosty i believe there are config files and plugins shared in the programming community to act as base templates to get a head start with your configuring..

p.s. good to see you...even though i see just your name and pacghost... :P

@dpreacher Yes there are. The Vim wiki is also really helpful when it comes to configuration stuff.

Good to see you too! Hope you’re doing well :D

Sign in to participate in the conversation

Linux Geeks doing what Linux Geeks do..