if your use case improves, use the remote client! I resorted to editing remotely using emacs, this reminds me.
my experience has made me believe that emacs machine hosting will become a bottleneck
however, the best SSH client can help ... try the list on OpenSSH.org (low in the left navigator) I like PuTTY on Windows, where selection = copy and right-click = paste.
not sure how to improve remote performance. The default build of emacs has a lot of lisp by default, but it requires more disk space than RAM space, and has always been effective for me, except for large files and net / sys lag.
If your case has backlighting and auto-updates that you do not need, then a minimal setup can help - it should be able to do this without recovery.
emacs is so extensive that I noticed the most when I found out that it can send / receive email. I barely examined the tip of the iceberg.
in this case, although “vi” might be better ... even with more emacs experience, I used small portions in each camp. I’m rarely a script or looking for a new function, digging is tough, but there are convenient guides for both.
Geekier
source share