4 ms·
I honestly don't understand the point. Emacs (much like VSCode or Idea) is a tool that I use for everything, all day. I don't see a point in shutting it down,
by nine_k 5y ago
I honestly don't understand the point.
Emacs (much like VSCode or Idea) is a tool that I use for everything, all day. I don't see a point in shutting it down, except for upgrading the version. Its startup time of, say, 15 or even 30 seconds (if you start many language servers) is only paid once, when I log in.
So I run it in server mode, and emacsclient start instantly, as a GUI window, or in a terminal, with all the amenities of an IDE already in place.
- giraffe_lady 5y agoJust different use cases then. Emacs isn't my main coding tool these days but I still use it for single-file editing, and I close it when I'm done with that file. The start up time does matter to me somewhat. Though I have a pretty simple config for the same reason and it's not bad enough for me to spend time on. I do keep an eye on it though.
- nine_k 5y agoThere are mini-editors that try to mimic emacs: https://opensource.com/article/20/3/lightweight-emacs https://opensource.com/article/20/3/lightweight-emacs (and more which I forget).
- ta988 5y agoUse the emacs server then. Start once use many.
- stjohnswarts 5y ago"emacs --daemon" and emacs-client are key to solving this scenario
- throw10920 5y agoI hope this doesn't come along as aggressive but: Do you really have a "different use case", or are you just averse to the idea of running it in the background as a daemon? Do you really need to save the 70 MB (without addons) to 200 MB (with addons) that it takes sitting there? Unlike bloated Electron apps, Emacs doesn't actually use CPU while you're not using it - it just sits there, takes up a little memory (and even on my old 4 GB RAM ThinkPad it's not enough to actually inconvenience me), and awaits you opening a new frame with emacsclient.
- giraffe_lady 5y agoI don't know I'm not an "emacs guy" really, I didn't know about this feature. It will probably work for me and I'll consider setting it up the next time I twiddle with my emacs config, something I do for an hour or two about once a year. But whether or not it solves my problem yes I think the use case is different? The person I responded to uses it so consistently they leave it running at all times. I can go days or weeks between single uses, depending on the projects I'm working on. That's a very different use to me.
- throw10920 5y agoAh, well, if you're going days/weeks between using it, then I understand why it wouldn't be useful for you to figure out how to configurate it more, and why leaving it running in the background would be mostly a waste. That makes sense. Although, now, I'm sure that many of us are curious - why would you only use Emacs this infrequently, but bother to use it at all?
- giraffe_lady 5y agoI used to use it a lot and do prefer it in the abstract. Just, my daily work has shifted to where I spend a lot more time exploring unfamiliar codebases, making small changes and refactors, and pairing in them. I work in a lot of different languages. Maintaining an emacs config that is truly very good at everything started to feel like a part time job on its own. Plus I work remote and for better or worse vs code has become conventional for remote pairing. So I have a minimal emacs config for when I don't need any particular language integration, and the rest of the time vs code is good enough for the daily work I actually do, which is rarely writing out features from scratch anymore.
- svnpenn 5y ago> Its startup time of, say, 15 or even 30 seconds Jesus. I use Gvim, which starts in less than a second. When I'm done editing, I close it. The only app I generally leave open, is browser. How people can justify such awful performance is beyond me, and why I will never, ever use Emacs.
- tarentel 5y agoWhile it can be very slow it's not something I even notice. When I start my computer, the terminal also starts on login, which means emacs starts. By the time I am ready to use it it loads instantly.
- nine_k 5y agoHow much code intelligence does GVim give you? Code navigation? Type information? Refactoring? The question is actually about IDE features which take longer time to initialize, mostly in the non-Emacs code such as language servers. Emacs with only built-in plugins loads from scratch instantly on my machine. But if I only need to do a simple quick edit, I can equally invoke vi :) (Which I regularly do, to keep my basic vi skills current.)
- golergka 5y agoLooks like you're judging a fish by it's ability to climb a tree.
- mcbuilder 5y agoSaid like such a vimmer. Anyway, my real comment is that I used vim exclusively for 5 years before switching to Emacs for like the past 9. I use evil mode to emulate vim of course. I'd run a server and ZZ or :wq as soon as I finished editing the file. My colleague, a regular Emacs user, commented how I drive emacs like vim in pair-coding. Now with vterm I run Emacs all the time, my buffers stay mostly open. Anyway, the best manner to use the tool is probably dictated by the tool, but I will tell you I am not bothered at all for my Doom Emacs 2 second starting time every few hours / days.
- forgotpwd16 5y agoFor Emacs to start that slow they probably load a ton of packages if not a framework like Spacemacs. If you just load simple settings, it opens instantly.
- stjohnswarts 5y agoI mean 90% of the problem is overcome just by running emacs server.
- deleted 5y ago[deleted]