burly.el VS ement.el

burly.el by u/alphapapa - might be an easier way to approach the current-window-configuration/set-window-configuration that Sacha has implemented

For the "lauch workspaces", I use burly which just uses simple bookmarks. Then with consult, I just use C-x b, then m to narrow to bookmarks and I have all the workspaces available (remote as well).

Well, that is essentially what Burly does: https://github.com/alphapapa/burly.el

Install https://github.com/alphapapa/burly.el

These features are especially useful with Burly: https://github.com/alphapapa/burly.el Because Burly can save and restore those kinds of windows, so you need not recreate them manually.

How does it compare to packages like burly, which (to my understanding) provide similar features?

I'm not sure exactly what you're looking for, but take a look at this: https://github.com/alphapapa/burly.el

I think you want "window configurations", which can be saved into registers. You might try tab-bar-mode for cycling through them. Or there's also https://github.com/alphapapa/burly.el/ . (I'd like something similar but haven't found something that matches what I want)

desktop is not a great solution for restoring buffers, because it generally only works for file-backed buffers. Instead, I wrote Burly to restore buffers, windows, and frames in mode-specific ways, on-demand using Emacs bookmarks. This is much more flexible and powerful than similar functionality in desktop.

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.