EquivalentCancel6 · 2022-05-17 17:29
So for a lot of reasons I've moved over from doom emacs to use my own personal emacs config and it's been pretty great so far. There is some sluggishness compared to say vim or even doom emacs and I'm wondering primarily how doom emacs makes their scrolling with evil mode soooooo smooth? For some reason it's kind of sluggish for me and I don't know why anyone got any suggestions/insights ?
LemonBreezes · 2022-05-17 19:04
Out of curiosity, what issues made you switch from Doom Emacs? I'm actually working on improving Doom Emacs and have some little ideas here and there.
EquivalentCancel6 · 2022-05-17 19:11
Good question - I kept running into weird inconsistencies when running the LSP for typescript or any language tbh :/. It would be running but the diagnostics weren't showing the errors on the current frame and I tried everything to resolve it.. turns out it's intermittent:/ so I opted for my own config that is very opinionated and very small compared to doom emacs
Now there are some really nice things I miss from doom.. especially since doom seems to be optimized for speed and being a newb to emacs idk how to tweak my emacs enough to make it really fast and efficient
LemonBreezes · 2022-05-17 19:25
I use LSP too for C++. Can you describe me what command I execute and what the expected output should have? Also, please provide your `~/.doom.d/init.el` file.
BadSlime · 2022-05-17 19:27
It's probably an optimization from a package that doom bundles, but I don't know for sure
EquivalentCancel6 · 2022-05-17 20:48
It's not so much a command it's more so the LSP frame/buffer, whatever you call them, inline diagnostics don't render/show anything at all.
For example if I have 2 imports in my TS file and I'm not using them, it will throw an error indicating that I have 2 imports that are not in use..
now with doom emacs I have to open the helm-diagnostic-buffer (I think that's what it's called) to see that the typescript lsp is throwing an error but the frame/window/buffer doesn't have any red lines which indicates there is an error somewhere in the file ...
I have no idea why this happens or how to solve it.. it's weird. The last time I had this issue I had to completely delete doom emacs and re-install it to fix it.
LemonBreezes · 2022-05-18 20:06
[Picture of Doom's LSP configuration](https://i.imgur.com/KTRmQlm.jpg)
Have you tried enabling the `+peek` flag for the Doom LSP module? I think it's the peek feature that you are referring to. I did not know about this myself.
EquivalentCancel6 · 2022-05-18 20:29
How do I even enable the \`+peek\` flag ? do i just do \`(lsp +peek)\` in \`init.el\` ?
LemonBreezes · 2022-05-18 20:33
Yup.
EquivalentCancel6 · 2022-05-18 20:34
well let's see if this fixes the problem.
LemonBreezes · 2022-05-20 14:33
Did it work?
EquivalentCancel6 · 2022-05-20 16:52
Well not really it seems to be an on and off sort of thing
LemonBreezes · 2022-05-20 17:47
You should raise this in the Doom Discord. There are people there that know more about Doom than I do.
Regarding this post though, one thing you can do is disable all of Doom's modules and roll your own private config on-top of vanilla Doom (an `init.el` with just `(doom!)`). That way you get some of Doom's optimizations.