From: Stephen Berman <Stephen.Berman@gmx.net>
To: bug-gnu-emacs@gnu.org
Subject: Re: gnu emacs 22.1 with xft: problems with background color of empty regions
Date: Thu, 05 Jul 2007 01:12:24 +0200 [thread overview]
Message-ID: <87wsxfix0n.fsf@escher.local.home> (raw)
In-Reply-To: 200707042018.l64KIlIw016409@kzsu.stanford.edu
On Wed, 04 Jul 2007 13:18:47 -0700 Joe Brenner <doom@kzsu.stanford.edu> wrote:
> I've compiled the emacs 22.1 source code on an amd64-based gnu/linux box
> (kubuntu), using the --with-xft and --with-gtk options:
>
> ../emacs-22.1/configure --with-gtk --enable-font-backend --with-xft --prefix /usr/local/emacs/xft_22.1
>
> I typically use a light-on-dark color scheme, but this has
> problems in this xft-enabled emacs. Empty regions on the screen
> are coming up a blinding white, ignoring my background color
> settings. Here's a screen shot:
This looks very much like what I used to get with gtk-qt-engine,
cf. http://permalink.gmane.org/gmane.emacs.pretest.bugs/18115. Are
you using this, since you're also using KDE?
> Note: a vanilla version compiled without xft support has no
> such problem:
>
> http://obsidianrook.com/data/emacs22.1-vanilla.jpg
I cannot account for the difference you describe (the pictures don't
show it, however; I assume the latter screen shot is mistaken). I
guess you built from the unicode2 branch, since the
--enable-font-backend and --with-xft options are not in the trunk.
Maybe the interaction with gtk-qt-engine there (if that's the problem)
is different from the trunk.
Steve Berman
next prev parent reply other threads:[~2007-07-04 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 20:18 gnu emacs 22.1 with xft: problems with background color of empty regions Joe Brenner
2007-07-04 23:12 ` Stephen Berman [this message]
[not found] ` <mailman.3079.1183590769.32220.bug-gnu-emacs@gnu.org>
2007-07-08 21:41 ` Joseph Brenner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wsxfix0n.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--cc=bug-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).