pashinin
indirect buffers
Workgroups2 become an indispensable tool — it works just great!
However, it doesn't handle indirect buffers well. It seems to not even differentiate between an indirect buffer and its original nor among different indirect buffers of the same original.
This can be verified most easily by typing
C-x 4 c
in (mostly) any major-mode you wish. Then store the workgroup, switch to another workgroup and then try to restore by switching back. Now, only one buffer, either the indirect buffer or the original buffer are restored twice. If you work with more than one indirect buffer the situation gets worse and when re-loading a wg-configuration from disk, you may end up with none of these buffers, not even the original being restored.
Working with indirect buffers is a basic and essential feature of emacs.
I think it should be addressed by the core code-base of workgroups2, rather than considering indirect buffers as some 'special buffers' for which some extra 'wg-special-buffer-serdes-functions' could be put in place. Actually, all those special-buffers may have indirect buffers as well.
All in all, I would be very thankful, if indirect buffers could be supported by workgroups2, or to receive comments how this could be best achieved.
It's cool that you like the extension. The situation is following... I do not have time to maintain workgroups. https://github.com/pashinin/workgroups2/issues/49
Also workgroups2 tries to do some low level stuff that should be done in Emacs C code (I believe). So if I ever get back to workgroups (and I want to) I'll try to write it in C and publish it as a patch or modified Emacs repo.
Thank you for answering. I have noticed your off-time banner.
However, I still posted the issue since it appeared rather general and possibly quite involved for a dirty hack. Still, if you may want me/other to point at where to start, maybe we could do something about indirect buffers.
Hope your comeback (whether with C or not) awaits us rather sooner than later. All best, mc