Extendable editing: ignore the rules.
I started work on Xtensis when I got tired of the current tooling for text editing. I felt a new contender was necessary that took inspiration from everything else, and turned them into a versatile idea.
(Side note: Xtensis was previously known as Slacs. It was changed to prevent ambiguity with Slack.)
Xtensis is currently being rewritten to be faster, more stable, and to be in line with Rust idioms.
Xtensis is intended to be as extendable as possible for the end-user. This is similar to GNU Emacs, but without the bloat and unnecessary features. Xtensis can have plugins that extend it whilst keeping the core subsystem small and lean.
Xtensis is designed to be minimal, and keep code in core to a minimum.
For example, GNU Emacs has the frontend and backend mixed together in an monolithic style. Xtensis is the opposite- the core runs in the background, and frontends can be attached to the core; the core does not care what frontend it is, as long as the communication between the frontend & the core is consistent and conforming to the standards.
This means that you could use a terminal-based frontend, Qt, Gtk, or, if you really wanted to- an Android frontend!
Xtensis should not hang. Asynchronous processing is vital in Xtensis, and it will make use of queues, and background processing.
Documentation for xtensis
You can read the documentation (gracefully hosted by ReadTheDocs.io) for Xtensis [here][rtd-xtensis].
Other documentation can be found in the
docs/ folder in the root of
At the time of writing this, Xtensis is in the process of being rewritten from scratch.
Xtensis is licensed under the GPL 3.0.
Contributing to Xtensis
Please see this document for more information about contributing to Xtensis.
The logo for Xtensis was designed by a friend of mine, @vktec
The logo is licensed under the CC BY-SA 4.0 license. Please provide attribution to @vktec for usage of it.
I have several sources of ongoing inspiration for xtensis: