A “I just want no input lag no matter how many packages I install. Its a frigging editor after all!! Is that too much to ask??”
B “Yes. (it’s an OS btw)”
A “Sigh.”
Two questions about your situation.
- How old is your computer? Does it have a decent amount of both processor speed and RAM?
- How large are the files that you have open that are giving you lag?
I am nowhere near a power user as I use only emacs for Org-Mode but even with a few of my insanely large PIM files (BookNotes.org which contains the notes and highlights to every every nonfiction books I have read in the last 10+ years) I have never encountered any lag in emacs.
I didn’t have any such issues since binary compilation became available.
Unless the package is a mode that’s actually active, I can’t see why packages would cause input lag.
I’ve noticed I have a lot of latency right after startup and the thing which seems to help is a manual garbage collect. That’s bit odd because the last thing I do in my config is set a 5 second timer which is fed a lambda to run a gc after the timer expires. Regardless, I still have better results if I run the gc manually.
I do load of metric ass ton of packages (and modes) and I recursively parse my Org/Org Roam directory for org-agenda items so I’m doing a lot of questionable things.
As others have said, sounds like we might both benefit by spending some quality time with the profiler.
As a minimal effort first attempts, I just installed XanMod kernel. If that makes a noticeable impact I will loop back here to report.
I had some latency and stuttering after 29 I started using gcmh and it works much better. Hopefully that will help you
flyspell on large org-file give serious input lag
Your eternal Emacs friend.
So stop sighing and start profiling.
The issue is almost always the gui, not any package. Input latency in the gui is awful but it’s fine in the tui
There’s a different read loop? I’ve not really noticed a difference tbh.
That can be profiled, too
Please. What is profiling?
That is not true. There are some features which makes only the GUI version slower, but it’s definitely not “almost always” that the GUI is the reason. There are a lot of features/packages which makes Emacs slower in general, no matter GUI/TUI.
So profiling, or bisecting the init file can be used find out the problem.
B “Yes. (it’s an OS btw)”
Haha, I absolutely hate it when people say that.
A “How can it be an OS if it hasn’t got a scheduler?”
B “Doesn’t need one, it hasn’t got threads.”
(I get zero lag myself BTW unless I’m connecting to an LSP server or something like that. Not since I gave up on using it for email anyway.)