Just curious about the workflow of other emacs users in Qubes.
Emacs is much more than just an editor, I use it to program, read my mail, as a todo app, personal wiki, read pdf and so on.
I’ve been struggling to split it in several qubes, because the strength of emacs is that it integrates so well with everything, like you can read your mail quickly press a keychord and that ends up in your org agenda as a todo reply item.
So far I did put everything emacs related into a standalone HVM but I was thinking of maybe having one Dev qube which contains an emacs just to code and another one dedicated to read email.
Splitting stuff like this means I lose integration with org-capture and org-agenda, I would end up with 2 agendas, not sure if it’s that bad yet.
I have a minimal Fedora TemplateVM that’s only got Emacs installed, then a disposable template with all my Emacs configuration and packages. Then I just spawn as many disposable Emacses as I need for each workflow from this template. I periodically enable networking on the disposable template, run it, and update the packages.
I have a persistent networked qube whose sole purpose is to occasionally package-install and package-refresh-contents, and then many offline writing/development qubes that copy over the packages from the networked qube’s ~/.emacs.d as needed. I am glad not to have a single overlord Emacs session, it is helpful/cleaner for project management. One Emacs qube per project or subproject. Perhaps I do lose a little synergy, as you note with org-capture and org-agenda. But the clarity is a win. And there’s always cross-qube copy/paste when needed.