Textadept

Glad to see this hit the front page again! I’ve been making some contributions lately and it introduced me to Lua. At its core it’s basically a very thin wrapper around the Scintilla editing component used by many open source editors. I’ve been working on getting some lower level APIs added for more control over the UI.

Mitchell is to be commended for maintaining the editor solo for so many years and keeping the LOC count really low (2000 lines of C, 4000 lines of Lua). If you’re willing to read the source it’s really easy to wrap your head around the whole thing, which can’t be said for Emacs or Vim. When I find the time I’ll finish my vi mode…

I've looked into TextAdept a few times. It appeals to me because it's got a standard Qt UI, is fast and lightweight and highly customizable with Lua. But I could never commit the time to fully customize it for daily use. Anyway, I'm committed to emacs. Other Scintilla-based editors with a similar feel (but missing the Lua angle) are Geany and Kate.

> Unlimited split views.

Ok, well now I have to find out what hapoens if I get enough splits to make the width of each less than a pixel.

I downloaded it recently and found it to be quite useful for quick notes. And I can attest to its "fast" claim, using it on a heavily monitored corporate computer, with CrowStrike and what-not; curiously, and I may being hyperbolic here, but, I got the feeling that it was opening faster than MS Notepad, even with Copilot disabled.

The only thing missing is for me is the "save temporary file" behavior, as I have this habit of making a quick note, close to save up space, both in RAM and view, then later on, fire it up again. Will see if there's a Lua api for this later.

I developed some plugins for Textadept some time ago. It's very lightweight and mature, but its dependence on different backends on different platforms introduced some frictions (QT vs. GTK etc.). We had a working Mermaid and image viewer plugin. It's really extensible. Never upstreamed them though.

It uses Lua LPEG lexers, which are extremely easy way to de develop syntax parsers/LSPs for new or unsupported languages.

Eventually our project moved to Pragtical, which has SDL as a cross-platform backend and uses the more modern meson as the build system, which made developing for it much easier.

There is also NotepadNext which is oddly similar, sans the Lua: https://github.com/dail8859/NotepadNext

Always nice to see open source text editors, in my opinion. Textadept's codebase is a fine example.

Check out Lite XL (also Lua-based)

[1] https://github.com/lite-xl/lite-xl

[2] https://lite-xl.com/

Shameless plug: For anyone interested in new code editors, I'm working on a multi-platform one called ecode [1]. It's similar in spirit to Notepad++ and Textadept, and some of the newer ones like Zed. It tries to be a fresh take using modern tools like LSP and DAP. I started it after using Geany for many years but finding it lacking some essential features for my needs. Speed is a big focus and it has very fast startup time.

[1] https://github.com/SpartanJ/ecode/

This is a great project! Is there a place to look up the list of inbuilt lexers to understand the editor language support? Will forward to my (more hands-on devs) team members.

What GUI text editor widget does it use, or is it home-grown?

I don’t see it mentioned.

Related. Others?

TextAdept - https://news.ycombinator.com/item?id=39571814 - March 2024 (31 comments)

Without any sarcasm, really, what is the value proposition in this one, that would make someone ditch Sublime Text for it?

Beautiful landing page

The features list mentions:

- Configurable key bindings, including language-specific keys, key chains, and key modes.

Does this include being able to make it feel like vi/vim?

I recommend capitalizing TextAdept, as it took me way way way too long to figure out it wasn't text a dept (SMS which department????)

Nice. Im looking for such projects. Will give it a try

Do we still need text editors in the AI agents era?

It uses Lua LPEG lexers, which are extremely easy way to de develop syntax parsers/LSPs for new or unsupported languages.

Eventually our project moved to Pragtical, which has SDL as a cross-platform backend and uses the more modern meson as the build system, which made developing for it much easier.

Always nice to see open source text editors, in my opinion. Textadept's codebase is a fine example.

Check out Lite XL (also Lua-based)

[1] https://github.com/lite-xl/lite-xl

[2] https://lite-xl.com/

> Unlimited split views.

Ok, well now I have to find out what hapoens if I get enough splits to make the width of each less than a pixel.

There is also NotepadNext which is oddly similar, sans the Lua: https://github.com/dail8859/NotepadNext

I recommend capitalizing TextAdept, as it took me way way way too long to figure out it wasn't text a dept (SMS which department????)

Beautiful landing page

Nice. Im looking for such projects. Will give it a try

Sounds like you're looking for the scratch file extension [1]

[1]: https://github.com/orbitalquark/textadept-scratch

tried this one: failed to open any file in my home directory, as it contains non-latin characters...

The splits functionality is one of its weaknesses right now IMO, but there are some improvements in the works.

[1] https://github.com/SpartanJ/ecode/

This is a great project! Is there a place to look up the list of inbuilt lexers to understand the editor language support? Will forward to my (more hands-on devs) team members.

The features list mentions:

- Configurable key bindings, including language-specific keys, key chains, and key modes.

Does this include being able to make it feel like vi/vim?

What GUI text editor widget does it use, or is it home-grown?

I don’t see it mentioned.

Related. Others?

TextAdept - https://news.ycombinator.com/item?id=39571814 - March 2024 (31 comments)

Without any sarcasm, really, what is the value proposition in this one, that would make someone ditch Sublime Text for it?

Do we still need text editors in the AI agents era?

Lexing is handled by one of Mitchell's other projects, Scintillua. You'll find the source for all the built-in lexers in there. https://github.com/orbitalquark/scintillua

The documentation for Scintillua also gets pulled into Textadept's API documentation as a dependency, so the syntax is also explained there. It's basically a bridge between Scintilla's native lexing and LPeg.

From the web page: You can also group key bindings into modes such that while a mode is active, Textadept ignores all key bindings outside that mode until the mode is unset (e.g. Vim-style modal editing). The keys documentation describes all of this in more detail.

It uses Scintilla. In fact, at its core, it’s basically just a wrapper around the Scintilla message passing API. There’s a Lua script that parses the Scintilla header files to create the Lua tables that interface with the Scintilla library.

? Seems to support GTK, Qt and ncurses?

looks like it uses scintilla

What's the point of this comment?

Can't speak to ditching a preferred text editor for this one, as text editors are one of the most highly personal preferences in computing.

But as a guy that teaches kids about computing and system administration, having another option to demonstrate is excellent. For many things something like nano is fine, but for something a bit more robust? And is available for many platforms? And is small and self-contained? It's a great option. The Lua extensibility is also a bonus.

Teaching teenagers how to use vim or emacs is, not surprisingly, a bit of a chore.

For starters, Sublime Text is closed-source. A better parallel would be something like Neovim, which also is extensible with Lua. What draws me to Textadept over Neovim is that it's intentionally kept very small, which means it's very easy to understand and extend. Contrast with Vim and its massive manual. However, like Emacs, almost everything is fair game for customization. For example, I wanted minimap functionality, so I implemented it:

https://github.com/Fwirt/textadept-minimap

Textadept's biggest strength is also its biggest weakness: Scintilla allows for a lot of features that are nigh-impossible in the likes of Vim and Emacs due to their reliance on terminal behavior. However, Scintilla is not terribly well optimized and does not support GPU rendering, meaning that while there is very little bloat, Textadept can still chug in some edge cases. The most notable instance right now is large files with no line breaks (e.g. minified js libraries). Other Scintilla-based editors also suffer from this to varying degrees, although Notepad++ has some performance optimizations that seem to mostly mitigate it. Notepad++ is also Windows only and not as easily extensible.

No sarcasm intended, but probably same reasons lots of people ditch sublime after trying it for a day;)

I haven't spent much time with it at all, but my very early impressions are:

- (Fairly) low memory footprint

- Nice approach to buffers which seems to borrow from vi

- Apparent very high extensibility using lua

Now, everyone can vibe code their own text editor.

We would need it when this era ends.

Sounds like you're looking for the scratch file extension [1]

[1]: https://github.com/orbitalquark/textadept-scratch

tried this one: failed to open any file in my home directory, as it contains non-latin characters...

If I was malware, one of the first things I'd do is check that scratch files directory for secrets.

The default behavior of Notepad++ is a very real security risk. So many system admins and developers will throw passwords and API keys into there and just forget about it. The scratch files are all sitting there unencrypted and with easy to exploit permissions.

Alas, my first thought after seeing TextAdept was that it could serve as a more secure alternative to Notepad++.

That is exactly it. Much appreciated.

Lexing is handled by one of Mitchell's other projects, Scintillua. You'll find the source for all the built-in lexers in there. https://github.com/orbitalquark/scintillua

The splits functionality is one of its weaknesses right now IMO, but there are some improvements in the works.

looks like it uses scintilla

Can't speak to ditching a preferred text editor for this one, as text editors are one of the most highly personal preferences in computing.

Teaching teenagers how to use vim or emacs is, not surprisingly, a bit of a chore.

https://github.com/Fwirt/textadept-minimap

Now, everyone can vibe code their own text editor.

We would need it when this era ends.

No sarcasm intended, but probably same reasons lots of people ditch sublime after trying it for a day;)

? Seems to support GTK, Qt and ncurses?

What's the point of this comment?

I haven't spent much time with it at all, but my very early impressions are:

- (Fairly) low memory footprint

- Nice approach to buffers which seems to borrow from vi

- Apparent very high extensibility using lua

hm... whole industry embraced its approach to palette of tools, dunno what you mean really :D I still try to avoid it for more than 10 years now, but is on all my compatible boxes.

of course, knowledge of VIM is essential to anyone when doing CLIs.

I saw that in the code on the github repo

oneeyedpigeon already explained it, but allow me to follow up with more information:*

You can see a zillion examples here: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

The purpose is to satisfy extra-curious readers (https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...) who might want to read previous discussions of the same story.

No criticism is intended! I add this because sometimes people think there's an implied "why did you repost this, it's already been discussed" - but not at all: reposts on HN are fine after about a year or so: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

* than you could possibly want, but oh well

dang is a mod—as far as I'm aware, they are the mod. When a previously-covered story crops up again, they typically add a comment like this with links to previous discussions, so you can easily see what was said before.

That is exactly it. Much appreciated.

If I was malware, one of the first things I'd do is check that scratch files directory for secrets.

Alas, my first thought after seeing TextAdept was that it could serve as a more secure alternative to Notepad++.

Legitimately curious, how would you implement a “secure” scratch file functionality? Or is it just that the whole notion of scratch files is insecure?

The great thing about Textadept’s extensibility (and use of Lua specifically) is that it’s easy to pull in other Lua modules to add functionality. I don’t think it would be much work to modify the scratch file extension to prompt you for an encryption key on startup and then run the scratch files through libsodium (via luasodium) if you want to have your cake (scratch files) and eat it (some cursory level of security).

I have this view as well. After years of Notepad++, the last security problem made me want to switch, not because of just that, but that, overall, since the author has an active voice expressing his political views (which is totally fine), I have this unease feeling that it makes him, and his products, a notorious target.

Searching for alternatives, Textadept seemed to fill the gap between features, speed and simplicity.

The plugin mentioned by the parent is really easy to grasp and tailor to my needs, which would not be the case with Notepad++, well, not for me at least.

I saw that in the code on the github repo

oneeyedpigeon already explained it, but allow me to follow up with more information:*

You can see a zillion examples here: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

The purpose is to satisfy extra-curious readers (https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...) who might want to read previous discussions of the same story.

* than you could possibly want, but oh well

hm... whole industry embraced its approach to palette of tools, dunno what you mean really :D I still try to avoid it for more than 10 years now, but is on all my compatible boxes.

of course, knowledge of VIM is essential to anyone when doing CLIs.

Searching for alternatives, Textadept seemed to fill the gap between features, speed and simplicity.

The plugin mentioned by the parent is really easy to grasp and tailor to my needs, which would not be the case with Notepad++, well, not for me at least.

one of the mods, along with tomhow!

Tell HN: Announcing tomhow as a public moderator - https://news.ycombinator.com/item?id=43558671 - April 2025 (462 comments)

I don't know anybody using Sublime:) what means "palette of tools"?

Legitimately curious, how would you implement a “secure” scratch file functionality? Or is it just that the whole notion of scratch files is insecure?

I use Joplin, which is a cross-platform FOSS notes app featuring E2EE. It's not a perfect solution and not much of a text editor, but it's the right direction.

Everything else is explicitly saved (without secrets) or just an ephemeral buffer in Neovim.

one of the mods, along with tomhow!

Tell HN: Announcing tomhow as a public moderator - https://news.ycombinator.com/item?id=43558671 - April 2025 (462 comments)

I use Joplin, which is a cross-platform FOSS notes app featuring E2EE. It's not a perfect solution and not much of a text editor, but it's the right direction.

Everything else is explicitly saved (without secrets) or just an ephemeral buffer in Neovim.

I don't know anybody using Sublime:) what means "palette of tools"?

Textadept is a fast, minimalist, and remarkably extensible cross-platform text editor for programmers.

Quick links: Download | Manual | Lua API Docs | Project Page

Features

Traditional desktop application written in a combination of C, C++, and Lua.
Runs on Windows, macOS, Linux, and BSD.
Self-contained executables – no installation necessary.
User-friendly graphical and terminal interfaces with sensible defaults.
Support for over 100 programming languages.
Multiple carets and selections.
Unlimited split views.
Configurable key bindings, including language-specific keys, key chains, and key modes.
Snippets, both generic and language-specific, and support for nested snippets.
Invoke shell commands for running code, building projects, and executing tests.
Almost every aspect of the editor can be scripted, extended, and customized with Lua.
Does not connect to the internet – it’s just a text editor!

Requirements

Textadept’s pre-built binaries require the following:

Windows 10+ (64-bit or ARM)
macOS 13+
Linux: Qt 5 or GTK 3 for the GUI version, and ncurses for the terminal version.

You can compile Textadept from source for use with different UI library versions, such as Qt 6 and GTK 2.24.

Note: Lua and other third-party dependencies are compiled into the application itself, and a Qt runtime is distributed with Windows and macOS builds.

Download

You can download pre-built binaries for various platforms, as well as source code from the links below.

| Stable Release
(13.0) | Unstable Release
(N/A) | Experimental

nightly build | | --- | --- | --- | | Windows | | Windows | | macOS | | macOS (Apple Silicon) | | Linux x64 / ARM | | Linux x64 / ARM | | Extra modules | | Extra modules | | Source code | | Source code |

A list of all released versions is here along with their release notes.

Note: while Textadept contains plenty of built-in productivity tools, some extra features and functionality are available as optional modules in the “Extra modules” links above. This includes:

Install and Use

Simply unpack the pre-built binary archive anywhere you have permission to and run one of the following executables:

Platform	GUI version	Terminal version
Windows	textadept.exe	textadept-curses.exe
macOS	Textadept.app
ta (shell script)	Textadept.app/Contents/MacOS/textadept-curses
Linux	textadept (Qt version)
textadept-gtk (GTK version)	textadept-curses

macOS Note: if you get a notice that Textadept “is damaged and can’t be opened,” you will need to remove the quarantine attribute from the app by running the following command in your terminal: xattr -d com.apple.quarantine /path/to/Textadept.app.

The “Help > Show Manual” menu item, or the F1 keyboard shortcut opens Textadept’s comprehensive user manual. There is also an online version. The manual covers all of Textadept’s main features, including installation, usage, configuration, theming, scripting, and compiling from source.

The “Help > Show LuaDoc” menu item, or the Shift+F1 keyboard shortcut opens Textadept’s extensive API reference for users interested in scripting the editor. There is also an online version.

If you downloaded the optional set of modules, unpack it into the .textadept/ directory in your home folder (keeping the top-level modules/ directory intact). You could instead unpack it into Textadept’s directory (thus merging the two modules/ directories), but this is not recommended, as it may make upgrading more difficult.

Note: Textadept generally does not auto-load modules. To use any of modules from the optional set, select the “Edit > Preferences”, use Lua’s require() function for each module to load, save the file, and restart Textadept. For example:

require('lsp')
require('file_diff')
require('spellcheck')

Compile

Compiling Textadept from source requires the following:

CMake 3.22+
A C and C++ compiler, such as:
- GNU C compiler (gcc) 8.1+
- Microsoft Visual Studio 2019 (16.8)+
- Clang 13+
A UI toolkit (at least one of the following):
- Qt 5.15+ development libraries for the GUI version
- GTK 2.24+ development libraries for the GUI version
- ncurses(w) development libraries (wide character support) for the terminal version
Unix patch command

Basic procedure:

Configure CMake by pointing it to Textadept’s source directory (where CMakeLists.txt is), specify a directory to build in, and optionally specify a directory to install to. CMake will determine what UI toolkits are available and fetch third-party build dependencies.
Build Textadept.
Either copy the built binaries to Textadept’s source directory or use CMake to install it.

For example:

cmake -S . -B build_dir -D CMAKE_BUILD_TYPE=RelWithDebInfo \
	-D CMAKE_INSTALL_PREFIX=build_dir/install
cmake --build build_dir -j # compiled binaries are in build_dir/
cmake --install build_dir # self-contained installation is in build_dir/install/

Note: if you would like to build the nightly development version of Textadept, enable the NIGHTLY option during the configuration phase (e.g. -D NIGHTLY=1).

The “Compiling” section of the manual contains more information about this process.

Support

Textadept is an open-source project, released under the MIT License.

You can contact me personally at code att foicica.com.

Hacker Times