You're viewing part of a thread.
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 $1a 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.
Those features aren’t enabled nor integrated. They’re added to Vim at its extensibility points.
And that has to be just about one of the pettiest to distinctions known to man.
It's still built to write code. Yes text is code, but vim is not a text editor in general,. It's made for programmers, nobody else is crazy enough to learn such obtuse syntax or want to have a developer with a scripting language built into it.
The features are in the editor. They are integrated with the editor. Yes, it's through plugins, but they're still part of the editor instead of part of some different program.
The word integrated literally just means you don't go into some other program to run your build.
It's an integrated environment for development.
It's an IDE!
It has debuggers.
It has syntax highlighting
It has compiling.
Even if you have to install them as plugins, it's designed to be doing all of those things.
And that has to be just about one of the pettiest to distinctions known to man.
If it's a petty distinction, why not acknowledge what I'm saying and move on? What is the point of this conversation for you?
It’s still built to write code. Yes text is code, but vim is not a text editor in general,
It's built to edit text, not just code. Yes, text is code, but Vim is a text editor in general.
The features are in the editor.
Once you put them there, yeah.
They are integrated with the editor.
Once you put them there, yeah.
Yes, it’s through plugins,
.
but they’re still part of the editor
..
It’s not petty, you don’t know what an IDE is.
i don't care if vim is an text editor or ide but i just wanted to ask if they even had debugger back when vim was created ?