Not in 10+ years has this been true, at least for me.
> You start Emacs and hope to never shut it down.
It's not hope for me. I start emacs when the machine starts and quite literally never shut it down. Not because I don't want to start it up, but because without it running, I don't get work done.
I even generally have a copy running in an (again) always-on tmux session, for when I login to a box via ssh.
I feel this "big bloaty" anti-emacs argument really lost its legs ~1989; I'm not sure why people cling to it unless they have a vested interest elsewhere.
Maybe I'm not using it right then, but I log in and out of these boxes several times a day from several different remote locations and just `tmux a` when I do.
How does emacsclient protect me from ssh disconnects? I thought all it did was use an existing emacs instance.
Not in 10+ years has this been true, at least for me.
> You start Emacs and hope to never shut it down.
It's not hope for me. I start emacs when the machine starts and quite literally never shut it down. Not because I don't want to start it up, but because without it running, I don't get work done.
I even generally have a copy running in an (again) always-on tmux session, for when I login to a box via ssh.
I feel this "big bloaty" anti-emacs argument really lost its legs ~1989; I'm not sure why people cling to it unless they have a vested interest elsewhere.