Closed robbyoconnor closed 6 years ago
Yup, I was right...it didn't work well for this...
Appears that 86b4e6f...65018ea have had some adverse side effects.
I think it should be something specific in your config that might causing it or the way you are using Emacs. I couldn't reproduce this issue with my config. I had two layouts open including the default one. Is that a problem?
I have the same problem. I reverted 4bb1d6ab3 commit temporarily.
I pushed a fix in develop branch, please verify :-)
It didn't help in my case. I reproduced this bug by following steps:
SPC b s
Also in *spacemacs*
buffer I can see that my settings for spaceline from my private layout weren't applied.
I got that too ^^. I believe it applies only to the home screen and not to all startup buffers.
Nope, it applies to other buffers too.
I was having an issue with the zerodark-theme this morning and its mode line. I rolled back to c12b72 and do not see the issue. @syl20bnr i pulled the latest develop but still saw the issue.
@rynffoll Like?
@Compro-Prasad I mean that my spaceline settings don't apply.
The layouts issue is fixed but I think these lazy loading introduced odd edge cases that need more testing.
I'm going to continue working from 86b4e6f76b062cbf921a617cc0eac5d73cb376a4
I mean that my spaceline settings don't apply.
Found the issue, opened a PR upstream: https://github.com/TheBB/spaceline/pull/198 Hopefully it will be accepted.
Basically all buffers that are created before spaceline is loaded and configured, will have a messed up powerline. Right now, only most of (not all) the startup buffers are explicitly set to the new modeline config after spaceline is ready but that's about it ("*Messages*", "*spacemacs*", "*Compile-Log*", but not "*scratch*" or any file buffer that was opened due to cmdline parameters):
One solution would be to extend that to all buffers or simply don't idle load spaceline.
Most of this lazy loading are micro-optimizations that don't add much value but are causing a whole lot of regressions.
On 06/13/2018 09:56 AM, Matthias Dahl wrote:
Basically all buffers that are created /before/ spaceline is loaded and configured, will have a messed up powerline. Right now, only most of (not all) the startup buffers are explicitly set to the new modeline config after spaceline is ready but that's about it ("Messages", "spacemacs", "Compile-Log", but not "scratch" or any file buffer that was opened due to cmdline parameters):
One solution would be to extend that to /all/ buffers or simply don't idle load spaceline.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/syl20bnr/spacemacs/issues/10849#issuecomment-396946351, or mute the thread https://github.com/notifications/unsubscribe-auth/AABaMMMKgRKiKoTjROm-sFhK_Hm-MDZgks5t8RoNgaJpZM4UicNe.
Basically all buffers that are created before spaceline is loaded and configured, will have a messed up powerline.
Should be fixed in last develop.
Should be fixed in last develop.
I can confirm it is fixed. Thanks (also for all the hard work and time you are investing into this project -- it is very much appreciated!).
I pushed a new way to load the spaceline fast enough at startup without lazy-loading it in commit https://github.com/syl20bnr/spacemacs/commit/d7f5b5889
Should close this issue.
Should I close this?
Sorry for not reporting back earlier but life got in the way (tm). From my side: Everything is back to normal wrt to spaceline/powerline, so if no one else has a problem, this can be closed.
Description :octocat:
Spaceline theme doesn't work with resumed layouts in broke in 4bb1d6ab391c89e772de526e5d4b45d013dc4a74...
Reproduction guide :beetle:
SPC q r
Observed behaviour: :eyes: :broken_heart: It shows in the Report-Issue buffer fine... but is wonky elsewhere
Expected behaviour: :heart: :smile: should look the same all over...
System Info :computer: