Corect me if I'm wrong, but you can't define macros in a couple key strokes or contribute to development of any modern IDE.
Nor they were designed to be hackable or customizable. If you open one of the setting sections in VS-Code you are presented with giant, over-engineered control panel with myriad of options you can toggle.
Where Vim has a blank canvas you splash with couple dozen lines of code to make it unique and personal. It's almost like you aren't using just vim, but your own hand-made editor built on a great minimal base, that is Vim.
> Corect me if I'm wrong, but you can't define macros in a couple key strokes or contribute to development of any modern IDE.
1. I did say most, not all
2. The main reason for macros I've seen is the lack of useful features in editors like vim. There are not that many repetitive tasks that you need macros that often. I think I used IDEAs macro recording once in the past 10 years
> Where Vim has a blank canvas you splash with couple dozen lines of code to make it unique and personal.
I:
- don't need "unique and personal", I need working out of the box
- don't want to "hack on my editor" to get the basic functionality I already usually have :)
> Almost everything you wrote is available for any modern IDE ... So they give all the things you mentioned ...
I guess, I've misread your comment somehow.
But anyway, my point is that modern IDEs can't give the same experience as or replace Vim, Neovim, Emacs. And while you don't need that experience, there are plenty of people who do. Nothing wrong with either side =-)
> my point is that modern IDEs can't give the same experience as or replace Vim, Neovim, Emacs
Every time I ask "what experience is that", all I get back is "unique editor" and "you can write macros for repetitive tasks".
No, thank you. I prefer the experience of an IDE that doesn't think that your code is plain text and offers tools that text editors stuck 30-40 years in the past know nothing about.
Any good Vim-emulator extension has macro support. VSCode also has an extension that lets you run the actual neovim server to manage your text buffer.
The settings GUI in VSCode is just an auto-generated layer over raw JSON files. You can even configure it to skip the GUI and open the JSON files directly when you open settings.
Nor they were designed to be hackable or customizable. If you open one of the setting sections in VS-Code you are presented with giant, over-engineered control panel with myriad of options you can toggle.
Where Vim has a blank canvas you splash with couple dozen lines of code to make it unique and personal. It's almost like you aren't using just vim, but your own hand-made editor built on a great minimal base, that is Vim.