-
Notifications
You must be signed in to change notification settings - Fork 55
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
Can't see default theme logs #281
Comments
Hah, looks like a update to the theme or Atom broke it. Thanks for reporting |
Hello, I have recently installed proton-mode on my work laptop (Ubuntu 17.04, Atom 1.12.2) and my home desktop (Manjaro, KDE Plasma, Atom 1.19.2). This same issue is visible on my home PC while in my work laptop is working as expected. If you could point me to any extra information or log I could provide I'll be happy to help. Regards |
If this theme has bugs in it, maybe a different one should be used for the default theme. |
happens to me too. Any workaround? |
The solution is to change the default theme to one that isn't buggy. I created a pull request for it. |
Hmm I wonder if we could just tweak the CSS instead of ripping out the theme. Let me review that PR |
The bug is in the theme's code, not our code. |
Some bugs in nucleus with the latest Atom causes boxes to be rendered incorrectly. As a short-term fix, the default theme is swapped back to atom-material References #281
Can someone please give #284 a try? If everything is fine I'll release it |
@dvcrn Whoops, missed that one. Going to try it at home. I didn't figure out which editor to stick to yet, found proton recently and seems to be what I'd like to use if I stick with Atom, so thank you! Sadly I've seen you switched to another editor, still with neovim? (kinda offtopic) |
btw if you like nucleus-theme you can try flexible-ui. It still well adaptive and I didn't found any issues with it for a long time. |
@dvcrn done testing, it works! |
The logs for the default theme do not appear. It's just a big empty box.
The text was updated successfully, but these errors were encountered: