phil-s

Ah, not quite done yet... set-window-point(1): (set-window-point@my-debug apply set-window-point set-window-buffer-start-and-point switch-to-prev-buffer replace-buffer-in-windows kill-buffer funcall-interactively call-interactively command-execute)

Sigh, this looks like an Emacs bug... `switch-to-buffer` only uses a marker from `window-prev-buffers` when `switch-to-buffer-preserve-window-point` is non-nil, but both `switch-to-prev-buffer` and `switch-to-next-buffer` call `set-window-buffer-start-and-point` using data from `window-prev-buffers`, and...

The upstream bug report is https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64911 Were it not for that, I suspect this PR would have been sufficient to resolve the issue entirely. As it is the current code...

> could we work around the problem by recording the point markers' positions and resetting from those Yes indeed -- and in fact I've done exactly that in the most...

We do still need to capture and reposition the markers, because we're not in control of the code which uses them to set the window point (in certain scenarios). So...

Can you confirm whether the pre-existing `section-ident` memory/restore is actually working for you? I was just failing to make the related change to my code, and when I test the...

I think I was missing the fact that the section identifier varies with the hierarchical structure, so when a room moves from, say, "Unspaced" to "Buffer" its ID has different...

Let's leave this for now. By accident it's ended up *not* being one of the patches I've been running locally, so I've not tested it recently and I don't want...

An `ement-reconnect` command would be great here, actually, if it's possible to retain all of the session buffers, connect the new session, and have the buffers associated with the new...

Thank you; I didn't get to this on the weekend, but expect to be able to test it this week.