4 ms·
This is the /real/ killer feature for me that I would find very difficult to live without and I don't know of any other editors that offer this functionality.
by jjrh 7y ago
This is the /real/ killer feature for me that I would find very difficult to live without and I don't know of any other editors that offer this functionality.
Being able to remotely open my editor (either from a terminal, or with X11 forwarding) with all the files I have open, exactly where I left off is incredibly useful.
- momentoftop 7y agoI never really learned screen because daemonised emacs sufficed for me. My daemon uptimes are normally the same as my system uptimes, with the one on my VPS currently at 77 days. A few years ago, I started using one daemon per project with server-use-tcp, each with a slightly different theme so I can easily tell them apart. (posted from emacs-w3m)
- jjrh 7y agousing emacsclient in screen or tmux is kinda handy if you're using a flaky connection and keep disconnecting (like on a train)
- h1d 7y agoAny benefit over using screen/tmux?
- jjrh 7y agoMain benefit is you don't need to remember to start your editor frame in screen/tmux and you can use both terminal and gui/x11. So when I'm at work I start emacs in X11 windows, when remote I simply ssh in and do emacsclient and connect to all the buffers I have open (if I have low latency i'll do x11 forwarding and start x11 emacsclient ) It's basically the same as tmux/screen but gives you a lot more flexibility. Other big benefit is starting emacsclient is basically instant, so opening a file from a webbrowser or whatever is super fast (some folks have 30 second or longer emacs startup times). Only real downside is it really sucks bringing back your state when emacs crashes and you have hundreds of buffers open for multiple projects across 20-30 emacs clients.