From: <osv@javad.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: Chong Yidong <cyd@stupidchicken.com>, 5679@debbugs.gnu.org
Subject: bug#5679: Emacs 23.1.93 pretest
Date: Wed, 10 Mar 2010 13:05:07 +0300 [thread overview]
Message-ID: <87pr3ch4q4.fsf@osv.gnss.ru> (raw)
In-Reply-To: <wl1vfsae53.wl%mituharu@math.s.chiba-u.ac.jp> (YAMAMOTO Mitsuharu's message of "Wed, 10 Mar 2010 15:23:36 +0900")
YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> writes:
>>>>>> On Thu, 04 Mar 2010 13:06:35 -0500, Chong Yidong <cyd@stupidchicken.com> said:
>
>> <osv@javad.com> writes:
>>> $ emacs -q --no-site-file
>>> - Move cursor to the /ABSOLUTELY NO WARRANTY/ text in the splash
>>> screen
>>> - M-x customize-face <ENTER> <ENTER>
>>> - Change "Font Family:" to "terminus"
>>> - Select "State|Set for Current Session"
>>> - C-x b <ENTER> to return to splash screen, and
>>>
>>> /ABSOLUTELY NO WARRANTY/ looks like in the attached file.
>
>> Fraid I still can't reproduce this. One possibility I can think of is
>> that the particular version of terminus you are using is buggy, and
>> reports the right overhang incorrectly. Strange...
>
> I tried installing the PCF fonts extracted from
> xfonts-terminus-oblique_4.26-2.1_all.deb to ~/.fonts on Mac OS X 10.6.
> The result was:
>
> 1. I could reproduce the above problem on Emacs 23.1.92.
> 2. But I could also reproduce it on Emacs 23.1, unlike OP.
No, I, the OP, can also reproduce it on Emacs 23.1. Here is what I wrote
in the original report:
" Small example screenshots from emacs 22.2.1 (correct rendering) and
emacs 23.1.93 (wrong rendering) are attached. Please notice how ugly
"Global Mark Ring" looks when rendered by emacs23.
NOTE: emacs 23.1.1 also renders wrong."
> 3. `xterm -fa terminus:style=oblique' showed the same problem.
> 4. I also tried my preliminary proof-of-concept cairo port (*)
> adjusted to Emacs 23.1.91, and it didn't show the problem. This
> explains why many GNOME and GTK+ apps don't show the problem with
> the same fonts.
>
> So, at least for my case, a possible explanation is that it is a
> problem in Xft drawing for some versions or settings. What's not
> explained is the inconsistency between the result 2 above and OP's
> experience with Emacs 23.1.
Emacs 23.1 behaves slightly different for me, but it still renders
wrong, so there is no inconsistency here.
-- Sergei.
prev parent reply other threads:[~2010-03-10 10:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pr3rny7e.fsf@stupidchicken.com>
2010-03-04 14:36 ` bug#5679: Emacs 23.1.93 pretest Sergei Organov
2010-03-04 15:57 ` Chong Yidong
2010-03-04 17:43 ` osv
2010-03-04 18:06 ` Chong Yidong
2010-03-04 19:22 ` osv
2010-03-09 0:05 ` YAMAMOTO Mitsuharu
2010-03-09 9:57 ` osv
2010-03-09 11:30 ` osv
2010-03-10 11:19 ` YAMAMOTO Mitsuharu
2010-03-10 11:29 ` osv
2010-03-10 11:54 ` YAMAMOTO Mitsuharu
2010-03-10 12:12 ` osv
2010-03-11 0:38 ` YAMAMOTO Mitsuharu
2010-03-10 6:23 ` YAMAMOTO Mitsuharu
2010-03-10 10:05 ` osv [this message]
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=87pr3ch4q4.fsf@osv.gnss.ru \
--to=osv@javad.com \
--cc=5679@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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).