1. Tramp. 2. Emacs daemon - as many suggest, why would you ever quit emacs? But if you do find you shut Emacs down... 3. Slimmed down alternative init eg. ht

1. Tramp. 2. Emacs daemon - as many suggest, why would you ever quit emacs? But if you do find you shut Emacs down... 3. Slimmed down alternative init eg. https://github.com/ocodo/.emacs.d/blob/master/emacsq https://github.com/ocodo/.emacs.d/blob/master/emacsq & https://github.com/ocodo/.emacs.d/blob/master/emacsq.el https://github.com/ocodo/.emacs.d/blob/master/emacsq.el (note this init could be even slimmer, but the start time is about 2.5 seconds, which is fast enough, and I get a very well configured environment) Or just ... 4. emacs -Q - no init. One of these are going to solve your issue, without having to interrupt your emacs flow. You could also look at your init for bottlenecks and have a secondary script. Which you can optionally run when you want those features. Keep the real init minimal. There's many strategies.