xt-editor / archived_xt-core Goto Github PK

At the moment, Xt is highly biased towards Emacs-style key
bindings.

In order to maintain high attraction to users, Xt must be
extensible in that regard.

Improve documentation for xtensis in general.
This includes (RTD) Sphinx, Rust docstrings, and the RFCs.

Xtensis needs logging.

There are numerous logging crates available on crates.io - it's just a matter of choosing the suitable one.

I think the Rope structure would be useful for slacs, as methods to store a buffer's contents is something I've been puzzling over.

I think it should be useful to use the Rope crate for slacs.

Just need to check licensing, IIRC XI-Editor (&Rope?) are Apache 2 licensed, contrary to slacs's GPLv3 licensing.

I have had a few people ask me with regards to Xtensis-

How the hell do I install it?!

This is a good question, and thus this issue is created to remind myself to improve documentation.

'slacs' sounds awfully like 'slack'

It's confusing, and quite a few people have spelled it wrong.

Thoughts?

At my college, I'm doing a Project Management unit, and for my "chosen project", I chose Xtensis. I have to rewrite Xtensis for it to be a valid project, however.

This is a good chance to rewrite Xtensis properly, and use good conventions.