Top Qs
Timeline
Chat
Perspective

Comparison of text editors

From Wikipedia, the free encyclopedia

Remove ads

This article provides basic comparisons for notable text editors. More feature details for text editors are available from the Category of text editor features and from the individual products' articles. This article may not be up-to-date or necessarily all-inclusive.

Feature comparisons are made between stable versions of software, not the upcoming versions or beta releases – and are exclusive of any add-ons, extensions or external programs (unless specified in footnotes).

Remove ads

Overview

More information Name, Developer ...
Remove ads

Operating system support

Summarize
Perspective

This section lists the operating systems that different editors can run on. Some editors run on additional operating systems that are not listed.

Cross-platform

More information Microsoft Windows, macOS ...
Remove ads

Natural language (localization)

More information Languages supported, Acme ...
Remove ads

Document interface

More information Multiple instances, Single document window splitting ...

Notes

  • Multiple instances: multiple instances of the program can be opened simultaneously for editing multiple files. Applies both for single document interface (SDI) and multiple document interface (MDI) programs. Also applies for program that has a user interface that looks like multiple instances of the same program (such as some versions of Microsoft Word).
  • Single document window splitting: window can be split to simultaneously view different areas of a file.
  • MDI: Overlappable windows: each opened document gets its own fully movable window inside the editor environment.
  • MDI: Tabbed document interface: multiple documents can be viewed as tabs in a single window.
  • MDI: Window splitting: splitting application window to show multiple documents (non-overlapping windows).
Remove ads

Basic features

More information Spell checking, Regex-based find & replace ...
Remove ads

Programming features

More information Syntax highlighting, Function list ...

Notes

  • Syntax highlighting: Displays text in different colors and fonts according to the category of terms.
  • Function list: Lists all functions from current file in a window or sidebar and allows user to jump directly to the definition of that function for example by double-clicking on the function name in the list. More or less realtime (does not require creating a symbol database, see below).
  • Symbol database: Database of functions, variable and type definitions, macro definitions etc. in all the files belonging to the software being developed. The database can be created by the editor itself or by an external program such as ctags. The database can be used to instantly locate the definition even if it is in another file.
  • Bracket matching: Find matching parenthesis or bracket, taking into account nesting.
  • Auto indentation: May refer to just simple indenting to the same level as the line above, or intelligent indenting that is language specific, e.g., ensuring a given indent style.
  • Compiler integration: Allows running compilers/linkers/debuggers from within editor, capturing the compiler output and stepping through errors, automatically moving cursor to corresponding location in the source file.
Remove ads

Extra features

Summarize
Perspective
More information Text shell integration, Graphical shell integration ...

Large file support:

Yes = Larger than 4 GiB (LFS) Yes2 GB = Larger than 1 GB, not limited by memory
memory = Limited by available memory    No (64 KB) = Some limit less than available memory (give max size if known)

In general, most text editors do not support large text files. Some restrict themselves to available in-core RAM while others use sophisticated virtual memory management techniques and paging algorithms.[96]

Search in files: Perform search (and possibly replace) in multiple files on disk, for example on a sub-directory and recursively all the directories below it. Similar to grep.

Remove ads

Key bindings

Summarize
Perspective

Support for custom key bindings.

More information Dynamically customizable, IBM CUA ...

Notes, bugs

  • Vim: custom maps of Ctrl-1 .. Ctrl-9, Ctrl-0 cannot be set, nor is Control-Shift-<char> distinguished from Ctrl-<char>.[116][117]
  • Notepad++: custom shortcuts of Shift-<char> cannot be set, they need an added modifier such as Ctrl or Alt. i.e. SCI_LINESCROLLUP cannot be bound to "Shift-I"as the "Add"button is greyed out.
  • Emacs and Pico: pico uses most of Emacs's motion and deletion commands: ^F ^B ^P ^N ^D etc.
Remove ads

Protocol support

Summarize
Perspective

Support for editing files over a network or the Internet.

More information FTP, HTTP ...
Remove ads

Unicode and other character encodings

Summarize
Perspective

To support specified character encoding, the editor must be able to load, save, view and edit text in the specific encoding and not destroy any characters. For UTF-8 and UTF-16, this requires internal 16-bit character support.

Partial support is indicated if: 1) the editor can only convert the character encoding to internal (8-bit) format for editing. 2) If some encodings are supported only in some platforms. 3) If the editor can only display specific character set (such as OEM) by loading corresponding font, but does not support keyboard entry for that character set.

More information ASCII, ISO-8859 ...
Remove ads

Right-to-left and bidirectional text

Summarize
Perspective

Support for Right-To-Left (RTL) texts is necessary for editing some languages like Arabic, Persian, Hebrew, and Yiddish and the mixture of left to right (LTR) and RTL known as bi-directional (BiDi) support.

Depending on the algorithm used in the programs it might only render the bidirectional text correctly but may not be able to edit them. (e.g. Notepad++ 5.1.3 shows bidirectional texts correctly but cannot edit it and user should change the text direction to RTL to be able to edit RTL texts correctly.)

More information Right-to-left (RTL), Bi-directional (Bidi) ...
Remove ads

Newline support

More information Windows (CR/LF), Classic Mac OS (CR) ...

See also

Notes

  1. [a]
    last update in OpenBSD repo[26]
  2. [b]
    No native support, available as a part of the Inferno port for Windows or by using `plan9port` over the WSL.
  3. [c]
    Requires Cygwin or the Windows Subsystem for Linux to run on Windows.
  4. [d]
    GEdit, when installed from MacPorts, runs in X11 and, therefore, does not have a native look and feel. However, precompiled native macOS binaries for GEdit may be downloaded from the GEdit project page, or from the GEdit FTP download server.
  5. [e]
    gedit, NEdit, and SciTE run in the X11 window environment, and therefore do not use the native Aqua look-and-feel when running on macOS.
  6. [f]
    Stand alone NSIS installable package is available
  7. [g]
    gedit supports single document window splitting via plug‑ins. Archived 2011-12-14 at the Wayback Machine.
  8. [h]
    gedit supports multiple document window splitting via plug‑ins. Archived 2011-12-14 at the Wayback Machine.
  9. [i]
    GNU Emacs 27.1 includes built-in support for tab bar (per-frame) and tab-line (per-window). Earlier versions of GNU Emacs can use a tabbed document interface in a non OS-native way using the Tabbar plug‑in.
  10. [j]
    GNU Emacs can support a tabbed document interface modelled after GNU Screen using the elscreen Archived 2008-01-17 at the Wayback Machine package.
  11. [k]
    JOE supports editing multiple files but only seeing one of them, and switching to others via Ctrl+K+N, which is functionally equivalent to having tabs but no visible tab bar.
  12. [l]
    mined supports Copy/Paste between multiple documents in separate windows, when these documents are in separate terminal windows
  13. [m]
    SciTE_max_buffers
  14. [n]
    Vim Provided GVim is used.
  15. [o]
    Vim version 7 supports a tabbed document interface. Earlier versions can emulate tabs through scripts, for example.[53]
  16. [p]
    Acme can invoke external commands and display their return values in order to integrate additional functionality.
  17. [q]
    ConTEXT does not support regular expression backreferences in its search and replace function. Archived 2007-12-18 at archive.today
  18. [r]
    ConTEXT only supports converting text to UTF-16. Also, it can only use one type of new-line format if converting to UTF-16.
  19. [s]
    Geany supports spell checking via a plug‑in
  20. [t]
    gedit supports spell checking via a plug‑in, which is distributed with gedit.
  21. [u]
    gedit supports Regex-based find & replace via plug‑ins ( Archived 2011-12-14 at the Wayback Machine).
  22. [v]
    Emacs supports spell checking via the external programs ispell, aspell, or Hunspell.
  23. [w]
    jEdit supports spell checking via an external plug‑in.
  24. [x]
    JOE supports spell checking via the ispell or aspell external plug‑ins.
  25. [y]
    JOE uses a non-standard regular expression syntax.
  26. [z]
    JOE can easily pipe text through the GNU recode(1) utility; it detects locale settings and allows editing in any encoding set up by the environment.
  27. [aa]
    Komodo Edit is based on Scintilla and may support virtual space similar to Geany and Notepad++ ()
  28. [ab]
    Komodo IDE is based on Scintilla and may support virtual space similar to Geany and Notepad++ ()
  29. [ac]
    LE can pipe text through the GNU recode(1) utility
  30. [ad]
    Metapad spell checking by calling external program Aspell.
  31. [ae]
    mined supports multiple lines in search and replacement expressions.
  32. [af]
    mined can convert the encoding format when using the Copy & Paste feature between multiple documents (that have different encodings).
  33. [ag]
    mined supports new-line conversion via a command-line option or from the menu. Files with mixed newline types can be edited transparently; different kinds of new-line have different visual indications.
  34. [ah]
    It is possible to start external applications from inside Sam and display their return values.
  35. [ai]
    Scintilla-based editors such as SciTE, Notepad2 and Notepad++ do not support alternation (
  36. [aj]
    UltraEdit uses the Boost C++ regex library. While Boost supports backreferences past \9 with \g{10}, UltraEdit has not yet implemented this feature.
  37. [ak]
    VEDIT 6.2 comes with Scribe spelling checker which has been written entirely in Vedit macro language. In addition, macro package for integrating Aspell can be downloaded here.
  38. [al]
    Vim version 7 supports spell checking natively. Earlier versions require a script.[64]
  39. [am]
    Visual Studio Code does not support virtual space, and rectangular selection beyond line endings is not possible.
  40. [an]
    Acme's auto-completion only works on file names.
  41. [ao]
    bluefish: Configurable via the outputbox feature.
  42. [ap]
    With external tool OpenCTags
  43. [aq]
    ed can invoke external commands, like a compiler.
  44. [ar]
    EmEditor Professional supports Auto Complete via plug‑ins (32-bit or 64-bit).
  45. [as]
    Geany uses its own tags file format, not compatible with ctags, see the manual.
  46. [at]
    gedit-folding: Folding plug‑in for Gedit
  47. [au]
    gedit: Compiler integration: Functionality in plug‑ins installed with gedit.
  48. [av]
    make can be launched from the LE text editor, but the output is not captured
  49. [aw]
    Evaluates expressions in some dynamic languages such as Clojure, Python and Javascript in realtime
  50. [ax]
    mined: Syntax highlighting: HTML/XML, Javascript, JSP.
  51. [ay]
    Notepad++ comes with Function List support, and it can be enhanced via plugins.
  52. [az]
    Notepad++ installs with auto complete list for multiple programming languages. Has user option to add additional personalized auto complete list(s).
  53. [ba]
    Function list (and stuff) available in Ru-Board build, ver 1.79.66Ru and later
  54. [bb]
    TextMate: Auto complete: Supported language bundles
  55. [bc]
    Textpad uses an add-on ()
  56. [bd]
    TextWrangler can integrate with a compiler if you write a shell script that takes flag input of the code and compiles it. You place this in ~/Library/Application Support/TextWrangler/Unix Support/Unix Filters/. It should show in the #! menu.
  57. [be]
    The Semware Editor: Auto complete: Supported via supplied/user-created lists.
  58. [bf]
    The Semware Editor: Text folding: Compressed view possible.
  59. [bg]
    Not in the Linux version.
  60. [bh]
    Vedit: Auto complete: Template editing, plus 3rd party macro for expanding symbols from tags database.
  61. [bi]
    Multi-line regex support Support for expressions spanning several lines (e.g. "\n\n(.+)\n\n")
  62. [bj]
    Alpha Macro support via AppleScript, Tcl or text factories.
  63. [bk]
    BBEdit Macro support via AppleScript, Perl, Python, Lasso, shell scripts or text factories.
  64. [bl]
    Coda offers macros via AppleScript, text "clips,"or plug‑ins (Cocoa apps or any installed scripting language).
  65. [bm]
    name
  66. [bn]
    Cssed Macro support via Python.
  67. [bo]
    jEdit: Limited by Java heap size.[81]
  68. [bp]
    Kate: Line length is limited by default. The limit can be removed, but long lines may cause poor performance.[84]
  69. [bq]
    LE text editor locks the file and warns if someone else has changed the file
  70. [br]
    LE text editor can view and edit large files or their parts in mmap-shared mode
  71. [bs]
    UltraEdit has no real limit on file size - and can easily open, edit, and save large text files in excess of 4 GB! .
  72. [bt]
    2GB with 32 Bits, on a 64 Bit system it depends on the available virtual memory.
  73. [bu]
    Emacs: 64-bit compilation on 64-bit OS can handle 2 GB files, otherwise the limit is 512 MiB.
  74. [bv]
    It is possible to customize all Gedit shortcuts because it is Gtk based.
  75. [bw]
    The JED base release comes with a basic CUA emulation, but it doesn't bother to bind lots of useful editor features. Also, like some other editors, 1 side of a region must be at the cursor. The main extension collections jedmodes/jed-extra and the "Red Project" have improved versions, tackling the former problem in particular.
  76. [bx]
    In SciTE, custom keystrokes may be assigned to Lua scripts, external programs or lexers (highlighters).
  77. [by]
    SlickEdit provides emulation of Visual Studio, Visual C++ 6, CodeWright, Epsilon and ISPF key bindings in addition to those given in the table.
  78. [bz]
    SlickEdit supports CodeWarrior, Xcode and BBEdit key binding emulation.
  79. [ca]
    SlickEdit includes support of vi key bindings, the ex command line and some, but not all Vim extensions.
  80. [cb]
    Vim emulates vi keys fully when in 'compatible' mode
  81. [cc]
    Vim With a script[110]
  82. [cd]
    when choosing e.g. Terminal font
  83. [ce]
    GNU Emacs: While GNU Emacs supports the UTF-8 encoding, it doesn't fully support the Unicode standard, since it doesn't fully support the Unicode Bidirectional Algorithm (see comment in the 'Right-to-left and bidirectional text' section below).
  84. [cf]
    GNU Emacs: While GNU Emacs supports the UTF-16 encoding, it doesn't fully support the Unicode standard, since it doesn't fully support the Unicode Bidirectional Algorithm (see comment in the 'Right-to-left and bidirectional text' section below).
  85. [cg]
    JEDs Windows version comes with a pair of scripts that can convert UTF-16 text files (actually anything iconv can convert) to and from JED's internal UTF-8. The Red Project releases include an enhanced version of these scripts.
  86. [ch]
    nvi Gentoo
  87. [ci]
    SciTE can open files in UTF or one single-byte encoding specified in a configuration file.
  88. [cj]
    TextPad can load and save UTF-8 and UTF-16 text files, but cannot use or even preserve characters outside of the system encoding.[125]
  89. [ck]
    when choosing e.g. New Courier font
  90. [cl]
    Vedit can convert UTF-8 and UTF-16 files to Windows character set and back. Characters not included in Windows charset can be preserved.
  91. [cm]
    Vim supports EBCDIC when compiled on a system that uses the EBCDIC character set.
  92. [cn]
    from version 21.5.29
  93. [co]
    GNU Emacs

    (1) According to a comment in the source file where the bidi support is implemented (http://git.savannah.gnu.org/cgit/emacs.git/tree/src/bidi.c accessed August 15, 2017), GNU Emacs doesn't fully conform to the Unicode Bidirectional Algorithm (Unicode Annex #9, a.k.a. UAX #9) in the way it wraps the lines of a bidi paragraph: "we are violating paragraph 3.4 of UAX#9. which mandates that line breaking shall be done before reordering each screen line separately."

    (2) According to the online GNU Emacs manual (section 22.19 Bidirectional Editing, accessed August 15, 2017), for the purpose of changing paragraph direction, "Paragraph boundaries are empty lines, i.e., lines consisting entirely of whitespace character". This contrasts with the otherwise ubiquitous convention of regarding the newline marker (LF on Unix derivatives, including macOS, and CR+LF on Windows) as the paragraph separator in plain text documents. However starting with version 26.0.50, the bidi paragraph separator can be customized.
  94. [cp]
    mined: supports bidi in cooperation with bidi terminal (mlterm, mintty); also supports "poor man's bidi mode"(automatic visual text order right-to-left input) in normal terminal
  95. [cq]
    Notepadpp: Scintilla (Notepad++'s Engine) does not really support bidirectional editing ... Some bidirectional text support added in 4.1.0. https://sourceforge.net/p/scintilla/bugs/757/#01c9
  96. [cr]
    GNU Emacs: GNU Emacs doesn't regard the newline marker as a paragraph separator in bidi texts. See comment in the 'Right-to-left and bidirectional text' section.

References

Loading related searches...

Wikiwand - on

Seamless Wikipedia browsing. On steroids.

Remove ads
Remove ads