|Some text editors support adequate plugin software that can include compilers, linkers, and toolchains altogether.|
My point is that a text editor is merely one component of an IDE. You can keep adding components (in the form of plugins) onto a text editor and eventually build something that functions as an IDE... but the text editor by itself is not an IDE.
Therefore... saying "Kate is my favorite IDE" is a little bonkers because Kate isn't an IDE. A more reasonable answer would have been "Kate with X, Y, Z, Q plugins is my favorite IDE".
|Even if not, you can manually compile the file without a toolchain, tools, etc. just from a plain .cpp file. |
Yes.... but then you're not using an IDE. You're just using a text editor and compiling manually.
I don't know if there's a formal definition of exactly what qualifies as an IDE or not... but I think that when most reasonable people talk about IDEs they're referring to something that has at least a few basic features:
1) A "code aware" text editor that includes at the very least some kind of syntax highlighting, but often also additional perks such as code completion, intellisense, etc.
2) Able to have multiple files open in the same context at once.
3) Has a concept of your entire program as a whole, rather than just the individual components. Whether that be through a project file, makefile or other means.
4) Has an interface with the build tools to where they can be easily invoked through the UI.
5) Integrated debugger.
Many text editors like Kate/Notepad++/etc can be pumped up with addons to fulfill several of these... but I don't think any of them fulfill all of them. Which is why they're not considered IDEs (at least not by anyone who actually uses IDEs).