Doom Emacs unresponsive for a few seconds when switching apps #15
Replies: 2 comments 1 reply
-
Does anybody have any suggestions please? These delays are making emacs pretty much unusable for me. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@kamransoomro84 If you are using Raycast, configure the "Search Menu Items" built-in extension to exclude Emacs from menu item scanning, or disable it entirely if you don't use it. This scanning process makes Emacs (and some other applications with many menu items) unresponsive. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I confirm that...
I searched the FAQ, issue tracker, discussions board, documentation, and wiki, and found nothing about my issue.
I read the debugging guide and researched the issue to the best of my ability.
My issue can be observed on the latest available commit of Doom.
My issue can be observed on a stable release of Emacs (i.e. doesn't end in
.50
,.60
, or.9*
)Describe your issue
I am running emacs on an M2 Mac. Whenever I switch to another app and then back to emacs, it becomes unresponsive for a few seconds. I have tried profiling it but do not see anything that might be blocking. I tried the sandbox and can confirm that the behaviour disappears in vanilla Doom but appears in Doom + modules - private config.
Not sure which modules might be causing the issue. My
init.el
file is below:Any tips would be welcome.
Steps to reproduce
System information
https://pastebin.com/VDXRymB9
Beta Was this translation helpful? Give feedback.
All reactions