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.”
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
That can be profiled, too
Please. What is profiling?
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.