Source code editor
|This article does not cite any references or sources. (February 2014)|
A source code editor is a text editor program designed specifically for editing source code of computer programs by programmers. It may be a standalone application or it may be built into an integrated development environment (IDE) or web browser.
Source code editors have features specifically designed to simplify and speed up input of source code, such as syntax highlighting, autocomplete and bracket matching functionality. These editors also provide a convenient way to run a compiler, interpreter, debugger, or other program relevant for software development process. So, while many text editors can be used to edit source code, if they don't enhance, automate or ease the editing of code, they are not source code editors, but simply text editors that can also be used to edit source code.
A source code editor can check syntax while code is being entered and immediately warn of syntax problems. A few source code editors compress source code, typically converting common keywords into single-byte tokens, removing unnecessary whitespace, and converting numbers to a binary form. Such tokenizing editors later uncompress the source code when viewing it, possibly prettyprinting it with consistent capitalizing and spacing. A few source code editors do both.
Some well-known source code editors
||This section may contain excessive, poor, or irrelevant examples. (February 2014)|
- Emacs (cross-platform, including Unix, Linux, Mac OS X, Windows)
- Geany (cross-platform, including Unix, Linux, Mac OS X, Windows)
- Gedit (cross-platform, including Linux, Mac OS X, Windows)
- IntelliJ IDEA built-in editor (Windows, Linux, Mac OS X)
- Microsoft Visual Studio built-in editor (Windows)
- Notepad++ (Windows)
- Sublime Text (cross-platform, including Linux, Mac OS X, Windows)
- TextMate (Mac OS X)
- vi/Vim (cross-platform, including Unix, Linux, Mac OS X, Windows)
Many source code editors and IDEs have been involved in ongoing arguments, sometimes referred to jovially as "holy wars" by the programming community. Notable examples include vi vs. Emacs and Eclipse vs. NetBeans. These arguments have formed a significant part of internet culture and they often start whenever either editor is mentioned anywhere.
- Integrated development environment
- Comparison of text editors#Programming features
- Comparison of hex editors
- Comparison of HTML editors
- List of text editors
|This text editor article is a stub. You can help Wikipedia by expanding it.|