Live data from Hacker News

Emacs 26.3

lists.gnu.org

161–165 of 165 posts

Re: Emacs 26.3

#161
I treat emacs as the only alternative to vim on the server. On your own GUI machine there are plenty of alternatives.

Do people recommend the use of emacs over vim on servers? (Mainly editing server config files and reading long logs) Any good plugins to enhance its use for this use case?

I have pretty much ignored emacs for the last 15 years when I felt it didn't act as snappy as vim.

Re: Emacs 26.3

#162
post #160
post #125

Earlier quoted context omitted.

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.

Any benefit over using screen/tmux?

Main 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.

Re: Emacs 26.3

#163
post #125

Earlier quoted context omitted.

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.

I 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)

using emacsclient in screen or tmux is kinda handy if you're using a flaky connection and keep disconnecting (like on a train)

Re: Emacs 26.3

#165
post #70

I tried vscode the other day to see what it's about and it's nice, but I found plugin development convoluted and very limiting compared to emacs. No chance of quickly writing a script to automate something in the editor, because it takes so much time that it's not worth it for quick editor code snippets. Other editor users simply have no concept of how easy it is to whip up some quick script to perform some task in e…

> Other editor users simply have no concept of how easy it is to whip up some quick script to perform some task in emacs. I don't want to start a flamewar, but I moved most things I was doing in Emacs to Textadept a while back because I found Textadept more convenient. That's not to say TA does everything you can do in Emacs, but it replaced all of the scripting I was doing with Emacs. You have the full power of Lua…

Which OS do you run Textadept on?
Post reply on HN