Skip to content
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

Lines aren't rendered with default background color after end of content #5428

Closed
th0br0 opened this issue Mar 9, 2016 · 10 comments
Closed

Comments

@th0br0
Copy link

th0br0 commented Mar 9, 2016

Description

Lines aren't filled with default line background color after the end of the line content. This was observed on pre-emacs-25 as well. Only manoj-dark and wheatgrass don't seem to have this issue. Background color differs between light/dark themes: either a bright or dark blue color.

Reproduction guide

  • Start Emacs

Observed behaviour:
bug

Expected behaviour:
Lines are filled with default line background color.

System Info

  • OS: gnu/linux, Fedora 25.
  • Emacs: 25.0.92.1
  • Spacemacs: 0.105.13
  • Spacemacs branch: master (rev. 2c3e6b4)
  • Graphic display: t
  • Distribution: spacemacs
  • Editing style: vim
  • Completion: helm
  • Layers:
(auto-completion better-defaults git markdown org
                 (colors :variables colors-enable-nyan-cat-progress-bar t)
                 emacs-lisp ess scala rust sql java
                 (python :variables python-enable-yapf-format-on-save t)
                 latex javascript html yaml shell shell-scripts typescript ansible dockerfile vagrant syntax-checking version-control polymode)
@korayal
Copy link
Contributor

korayal commented Mar 21, 2016

This may be directly related to Emacs (or GTK). I'm getting the same issue even if I run emacs -Q and manually set the background to red the frame background turns black. If i set it to white, the frame becomes blue

@d12frosted
Copy link
Collaborator

@korayal what version of Emacs are you using?

@th0br0
Copy link
Author

th0br0 commented Mar 21, 2016

As far as I know, that's highly likely (or at least it's one of the reasons). There's an open upstream ticket at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20882

@korayal do you happen to be using xmonad?

@korayal
Copy link
Contributor

korayal commented Mar 21, 2016

@d12frosted I'm using emacs-24.5.1 but I also tried out emacs-snapshot package in ubuntu xenial and the issue is still there.

@th0br0 I'm on gnome 3.19.90 but I had the same issue on xmonad too.

@korayal
Copy link
Contributor

korayal commented Mar 28, 2016

UPDATE: I installed emacs24-lucid instead of emacs24 and it started working alright. I think this issue is about GTK

@danielrenninghoff
Copy link

I also ran into this issue yesterday on Fedora 24. Todays update to gtk3-3.20.2 has fixed the issue though, so this doesn't seem to be an emacs or a spacemacs bug.

@StreakyCobra
Copy link
Contributor

@th0br0 Can you also try if updating gtk fixes your issue?

@korayal
Copy link
Contributor

korayal commented Apr 4, 2016

I switched back to emacs24 again and it seems the gtk update did the trick.

@Aletheia-Lothlorien
Copy link

Had the same issue with OpenSuse Tumbleweed. Upgraded gtk today and now back to normal.

@StreakyCobra
Copy link
Contributor

Closing as this issue is fixed upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants