A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!
This is pretty much exactly what I do. The only real hiccups I can think of:
If you use Org Roam the different machines will have their own Sqlite databases and thus you may need to do an org-roam-db-sync when hopping.
org-agenda may need to be refreshed when hopping machines.
I have bound keys for both of those things to make the manual portion as non-disruptive as possible.
Why did you make three threads with the same content?
the new config is synced to the other machines
I don't know man; how do you plan to sync those machines? If you have 4 machines involved, there are always problems with machines being online/offline and talking to each other that you will have to solve somehow. If I were you, I would make a public or private repo on Github and use git to version control your content. You can push/pull from each machine when you make changes and need to propagate those changes. You can potentially automate the process of pushing and pulling via shell or elisp script.
Would that work in practice or are there pitfalls I am not aware of?
The most important thing is to keep eyes on your paths when it comes to documents and packages. I suggest keep all your org files in one directory, say ~/documents or whatever you prefer, and keep all of your Emacs config in .emacs.d, so you can just push/pull the entire .emacs.d. Another thing to keep eye in your config on are external programs, ag, ripgrep, etc. Since you are basically in the *nix world, it shouldn't be too difficult, but there still might be differences where they are found etc; so you might need to keep an eye on paths and which programs you use. You can solve it in different ways, at your discretion, either directly in Emacs setup or in your login shell.