4 ms·

Just 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 fil

Just 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 ago
There 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 ago
Use the emacs server then. Start once use many.
stjohnswarts 5y ago
"emacs --daemon" and emacs-client are key to solving this scenario
throw10920 5y ago
I 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 ago
  I 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 ago
    Ah, 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 ago
      I 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.

nine_k 5y ago

There 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 ago

Use the emacs server then. Start once use many.

stjohnswarts 5y ago

"emacs --daemon" and emacs-client are key to solving this scenario

throw10920 5y ago

I 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 ago
I 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 ago
  Ah, 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 ago
    I 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.