I’m trying out Obsidian for taking notes, and this made me laugh.
You’re not a normal text editor if you have a built in scripting language.
I’m not a text editor. But anyway, would you call a shell script that invokes python.exe $1 a Python IDE? Why would you? Vim isn’t designed to facilitate the use of vimscript, vimscript is just an extensibility feature of Vim.
Vim isn’t designed to facilitate the use of vimscript, vimscript is just an extensibility feature of Vim.
Vim is designed to edit code, by the people who were doing it back in the 70s and all of its features are there to enable better, faster, and more efficient editing.
It has scripts for the sake of those scripts enabling integrated developer features. Because they’re part of vim they’re in the environment and the program is used predominantly for development.
Vim is designed to edit code
To edit text files. It doesn’t matter if it’s code, configuration files, or plaintext. There are no interpreters, no compilers, no debuggers, nothing designed to support any particular framework or language or workflow. All of that is possible to add through the extensibility features.
Vim is a highly configurable text editor built to make creating and changing any kind of text very efficient.
Vim is an advanced text editor that seeks to provide the power of the de-facto Unix editor ‘Vi’, with a more complete feature set.
Vim is a highly configurable text editor built to enable efficient text editing.
Vim is a text editor which includes almost all the commands from the Unix program “Vi” and a lot of new ones. It is very useful for editing programs and other plain text.
– https://vimhelp.org/intro.txt.html#intro.txt
–
It has scripts for the sake of those scripts enabling integrated developer features.
Those features aren’t enabled nor integrated. They’re added to Vim at its extensibility points. Baseline vim doesn’t have them.
