Stéphane Marks
Stéphane Marks
See PR #53 which supersedes #49 which I will now rescind.
@pinaceaepinus try this branch shipmints-frame-handler-name-geometry-logic from https://github.com/shipmints/bufferlo.git and see if this addresses your frame name (and potentially geometry) issues. Follow the procedure here or use your own, similar, method https://github.com/florommel/bufferlo/issues/46#issuecomment-3461510493
Try setting `bufferlo-bookmark-frame-load-make-frame` to `'reuse-restore-geometry`. The updated documentation is in the branch I shared with you. I should have been clearer.
bufferlo sets with multiple frames use the Emacs frameset package to persist frames and you can either use Emacs's own geometry handler or the bufferlo one. There are two user...
It's definitely a suggestion to look at the two user options mentioned. That it might be confusing is something we can refine over time, if we choose to unify bufferlo...
Yes, the whole thing is tricky. We can collapse these in the future as bufferlo users move to Emacs 31+.
@pinaceaepinus, can you give the PR #49 a try and see if this resolves the issue with frame names and geometry when loading a set?
What I do is this: ```shell mkdir ~/proj/shipmints-github/bufferlo cd ~/proj/shipmints-github/ # this is where the branch lives until the PR is merged git clone https://github.com/shipmints/bufferlo.git git switch shipmints-restore-frame-specs-during-set-loading ``` ```elisp...
#53 supersedes #52 so take the branch above to try "shipmints-frame-handler-name-geometry-logic".
Thank you for testing. We will merge #53.