ement.el VS unpackaged.el

Please see https://github.com/alphapapa/ement.el/issues/55

Only login limitation might be from the lack of support for SSO https://github.com/alphapapa/ement.el/issues/24 but judging from the issue it looks like SSO logins in ement.el will be coming shortly

I tried out ement recently and boy it's slick. Easily the best interface to Matrix I've used on a personal computer. Alphapapa doesn't miss.

It doesn't support single-sign-on (SSO) yet, but this is being tracked in https://github.com/alphapapa/ement.el/issues/24. If you can chime in and help test the code there, that could help get support merged sooner.

This is very interesting. I've been thinking about using an AVL tree in Ement.el for the lists of events in each room, because they need to be used in-order by timestamp, and they can be received in any order (e.g. when loading older events), and it wouldn't be good to re-sort the whole list after each insertion. As it stands, each event is effectively sorted at the time it's inserted into a room's buffer (which may be never, depending on whether the room has an open buffer), and it works well enough, but I wonder if it could be improved.

The question is almost like asking a fish to describe water. It's the sudden lack of it that produces a really clear example. :)

Anyway, here's a random example that comes to mind: I have some sexps in a Lisp file and I want to sort them alphabetically. Each sexp (usually a top-level form, but not necessarily) usually spans multiple lines, so line-sorting won't do it. Since they may be top-level forms, there may be comments between them that would lose their context if their position relative to sexps were lost, so comments need to "stick to" sexps they're above.

How would you solve this in a random text editor?

In Emacs, I would develop a command that does what I need. At each stage of the development process, I evaluate the command's definition, and it's instantly available to be used and tested. I could even test the function on its own definition, if I wanted to be silly (undoing the sorting after testing, of course).

When I'm done, I save the command definition to my configuration, and it's now a permanent tool in my toolbox. I didn't have to recompile the editor and start a new process, nor did I have to submit a patch to an upstream and ask for it to be merged. Similarly to a carpenter (forgive me if it sounds silly), my editor is my workbench, and as wood is malleable, so is my editor.

So, here's the command I came up with (maybe not the prettiest implementation, but maybe not the worst): https://github.com/alphapapa/unpackaged.el#sort-sexps And using Emacs and Org mode, I publish it into this "unpackaged" package, which I then install into my configuration as a package, and other users can then easily install it into theirs, too.

I don't know of any other editor that can do all of this, certainly not so easily.

Here's the code in my Emacs config. I'll probably add these functions to unpackaged.el (the Org sorting function there is more primitive than these).

Sorting. This is handled within Org, see org-sort. However, you may find this function helpful for sorting recursively and with multiple methods (e.g. first by priority, then alphabetically): https://github.com/alphapapa/unpackaged.el#sort-tree-by-multiple-methods-at-once

The customize buffers can be used with the keyboard. You can tab between fields, and C-c C-c to set values. See also https://github.com/alphapapa/unpackaged.el#set-value-of-customization-option-at-point