all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: <osv@javad.com>
Cc: Chong Yidong <cyd@stupidchicken.com>, 5679@debbugs.gnu.org
Subject: bug#5679: Emacs 23.1.93 pretest
Date: Wed, 10 Mar 2010 20:54:36 +0900	[thread overview]
Message-ID: <wl1vfs9ytf.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <87lje0h0so.fsf@osv.gnss.ru>

>>>>> On Wed, 10 Mar 2010 14:29:59 +0300, <osv@javad.com> said:

>> Anyway, is `xterm -fa terminus:style=oblique' also broken?  If so,
>> we can conclude this is not a bug at the Emacs side.

> Yeah, this is broken as well. So please excuse my ignorance, but
> where exactly the problem is?

According to the experiments so far, it seems to be caused by Xft in
addition to some conditions that are not yet sure (maybe library
versions or settings?).

> I.e., why emacs 22 renders it fine?  What is a work-around for emacs
> 23?

Emacs 22 uses the traditional text drawing aka X core fonts, and many
GNOME and GTK+ applications use cairo rather than Xft.  A workaround
would be to use the traditional text drawing as in Emacs 22 by
preferring the X core font driver to the Xft one (see `fontBackend' in
the "Table of X Resources for Emacs" node in the Emacs info).

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp






  reply	other threads:[~2010-03-10 11:54 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27  3:40 Emacs 23.1.93 pretest Chong Yidong
2010-02-27  9:05 ` Eli Zaretskii
2010-02-27 10:21   ` Eli Zaretskii
2010-02-27 11:28     ` Juanma Barranquero
2010-02-27 12:11       ` Juanma Barranquero
2010-02-27 13:15         ` Eli Zaretskii
2010-02-27 14:14           ` Eli Zaretskii
2010-02-27 14:31           ` Andreas Schwab
2010-02-27 14:54             ` Eli Zaretskii
2010-02-27 14:59               ` Lennart Borgman
2010-02-27 15:29                 ` Eli Zaretskii
2010-02-27 15:22           ` Chong Yidong
2010-02-27 18:58             ` Eli Zaretskii
2010-03-04 11:32             ` Kenichi Handa
2010-03-04 12:35               ` Jason Rumney
2010-02-27 15:39           ` Juanma Barranquero
2010-02-27 19:41           ` Stefan Monnier
2010-02-27 11:57     ` Eli Zaretskii
2010-02-27 19:03       ` Eli Zaretskii
2010-02-27 21:37         ` Chong Yidong
2010-02-27 22:22           ` Eli Zaretskii
2010-02-28  1:25             ` Chong Yidong
2010-02-28 17:21               ` Eli Zaretskii
2010-02-28  1:45             ` Chong Yidong
2010-02-28 10:46               ` Andreas Schwab
2010-02-28 14:25                 ` Chong Yidong
2010-02-28 15:38                   ` Andreas Schwab
2010-02-28 17:32                   ` Eli Zaretskii
2010-02-28 19:31                     ` Eli Zaretskii
2010-03-02 18:15                       ` Eli Zaretskii
2010-03-02 19:53                         ` Chong Yidong
2010-03-02 20:53                           ` Eli Zaretskii
2010-03-04 11:24                             ` Kenichi Handa
2010-02-28 17:34                   ` Eli Zaretskii
2010-02-28 21:34                     ` Chong Yidong
2010-02-28 17:15               ` Eli Zaretskii
2010-03-02 15:42 ` Drew Adams
2010-03-02 16:02   ` Chong Yidong
2010-03-02 18:35     ` Drew Adams
2010-03-02 19:53       ` Chong Yidong
2010-03-04 14:36 ` bug#5679: " 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 [this message]
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

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=wl1vfs9ytf.wl%mituharu@math.s.chiba-u.ac.jp \
    --to=mituharu@math.s.chiba-u.ac.jp \
    --cc=5679@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=osv@javad.com \
    /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.