From: Stephen Berman <Stephen.Berman@gmx.net>
To: emacs-devel@gnu.org
Subject: (re)display problems after font backend merge
Date: Thu, 15 May 2008 20:45:17 +0200 [thread overview]
Message-ID: <87fxsjmmo2.fsf@escher.local.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
Since Kenichi Handa's font backend merge yesterday I see different, and
at least partly buggy, display and redisplay effects. This shows up
clearly in some of my customizations, in particular of the mode line and
the Gnus Summary buffer. The following screen shots show the
differences; the top image is post-merge, the bottom pre-merge:
[-- Attachment #2: Post-merge display --]
[-- Type: image/png, Size: 18836 bytes --]
[-- Attachment #3: Pre-merge display --]
[-- Type: image/png, Size: 18672 bytes --]
[-- Attachment #4: Type: text/plain, Size: 942 bytes --]
Here is a description of the differences I see:
- In the post-merge image, the underlining I use in the mode line is
broken, as is the underlining of the current article in the Gnus Summary
buffer, and the latter underlining touches the bottom of the characters
in the post-merge image, while there is a (IMO more pleasing) space in
the pre-merge display.
- The fringe arrow in the Summary buffer is redisplayed in the mode
line.
- The character size in the mode line is larger in the post-merge image
than in the pre-merge image (in both it is font family Helvetica).
- The appearance of the non-ascii characters I use for threading and
separation in the Summary buffer differs; in particular, the separator
forms a broken vertical line in the post-merge buffer, while it is a
continuous vertical line in the pre-merge buffer (except for the line
containing the Indic characters, which is also misaligned in both
images).
Steve Berman
next reply other threads:[~2008-05-15 18:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 18:45 Stephen Berman [this message]
2008-05-16 0:57 ` (re)display problems after font backend merge Kenichi Handa
2008-05-16 10:22 ` Stephen Berman
2008-05-17 3:19 ` David De La Harpe Golden
2008-05-17 12:30 ` Stephen Berman
2008-05-17 14:02 ` David De La Harpe Golden
2008-05-17 18:37 ` Stephen Berman
2008-05-18 3:30 ` David De La Harpe Golden
2008-05-18 18:19 ` Stephen Berman
2008-05-22 20:36 ` Stephen Berman
2008-05-23 4:16 ` David De La Harpe Golden
2008-05-23 12:28 ` Stephen Berman
2008-05-23 16:10 ` David De La Harpe Golden
2008-05-23 17:03 ` Stephen Berman
2008-05-23 17:37 ` David De La Harpe Golden
2008-05-23 19:42 ` James Cloos
2008-05-23 20:41 ` Stephen Berman
2008-05-23 21:57 ` David De La Harpe Golden
2008-05-24 1:16 ` James Cloos
2008-05-24 23:01 ` Stephen Berman
2008-05-27 13:17 ` Stephen Berman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fxsjmmo2.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.