-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing theme takes too long #84
Comments
I don't quite get it. How do you change the theme? With |
No. Evaluate loads theme from within emacs with another theme. |
This seems to be caused by the extra frames (workspaces) created by EXWM. Can you confirm it? |
How could I? ehmmm shall I like just use one workspace? |
@ch11ng I just tried using only one workspace, indeed it's that what is causing the delay, I was using 10 workspaces. How can this be solved? D: is this an emacs issue more than EXWM? |
I don't quite understand the mechanism of changing color theme in Emacs, but it seems |
I guess using EXWM with only one frame and some kind of perspectives then would be a more fitting solution for work spaces for me. |
I'm just curious how often you change the color theme. I think one usually select a color theme an stick to it for months or even years. Besides, loading the color theme should probably always be done at startup since changing the color theme at runtime may cause some side effects. Now that this issue is not related to EXWM, I'm closing it. |
It's also very slow when opening Magit Status...I now reverted to having only one workspace and magit status loads very quickly. |
Perhaps hiding unused workspaces would help, but I'm not sure. |
can you replicate the magit status delay though? |
No, at least unnoticeable with even 10 workspaces. |
I have been experiencing this since day one but I always thought it was an Spacemacs issue, but after using an ubuntu machine with my same configuration I think it is EXWM the one it's doing something to the loading time for changing themes.
The text was updated successfully, but these errors were encountered: