unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David De La Harpe Golden <david@harpegolden.net>
To: matthew@ssl.co.uk
Cc: 8426@debbugs.gnu.org
Subject: bug#8426: Glyph and cursor problem with emacs
Date: Tue, 05 Apr 2011 20:41:28 +0100	[thread overview]
Message-ID: <4D9B7068.3000002@harpegolden.net> (raw)
In-Reply-To: <4D9AE9A6.2010401@ssl.co.uk>

On 05/04/11 11:06, Matthew Carey wrote:

> My other box with the same OS and architecture does not exhibit the problem.

The exact same architecture?  Particularly, same gfx card and same 
version of said driver for said card, with same xorg.conf config 
options?  It's just the perennially annoying closed x11 drivers for 
ati/amd and nvidia hardware often have bizarre 2D drawing glitches, and 
they can be dependent on the precise version, configuration options 
(like which AccelMethod is in use) and whether compositing is enabled 
[1][2] (in contrast, the open drivers are typically slow for 3D but 
really good for 2D)

> 2 No other applications seem to be affected this way on the box.

That _could_ be just luck / the subset of apps used by the driver 
authors for testing coinciding with yours.  Emacs handles its own 
drawing to the main window with direct xlib calls, and may do things 
legally but still differently to some other apps.

> If I use the same emacs installation forwarding X output to another machine it
> works fine.

Well, as Eli points out, that does strongly suggest it's an X server 
level problem, not an emacs problem.  If it were, say, some call to 
XFillRectangle being misplaced in the emacs binary you'd expect it to 
occur on all X servers you tried.

The chances of DejaVu Sans Mono metrics being messed up seem slim, and 
also xft/xrender based font rendering, unlike the old core x11 
server-side font rendering, uses client-side tesselation to trapezoids 
and you say the same emacs works on another x11 server, so that's not 
the problem. While it's been actively developed (descended from 
Bitstream Vera) and therefore there are different versions of it 
floating about, it's an extremely widely used font, and the one I use 
with emacs with no such problems.

[1] http://ati.cchtml.com/
[2] 
https://wiki.archlinux.org/index.php/ATI_Catalyst#Catalyst_10.6.2F10.7.2F10.8.2F10.9_:_black.2Fgrey.2Fwhite_boxes.2Fartifacts_in_firefox.2Fthunderbird





  parent reply	other threads:[~2011-04-05 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 10:06 bug#8426: Glyph and cursor problem with emacs Matthew Carey
2011-04-05 16:57 ` Eli Zaretskii
2011-04-05 17:08   ` Matthew Carey
2011-04-05 17:20     ` Eli Zaretskii
2011-04-06 10:16       ` Matthew Carey
2011-04-06 15:15         ` David De La Harpe Golden
2011-04-05 19:41 ` David De La Harpe Golden [this message]
2019-10-01 16:39 ` Stefan Kangas

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=4D9B7068.3000002@harpegolden.net \
    --to=david@harpegolden.net \
    --cc=8426@debbugs.gnu.org \
    --cc=matthew@ssl.co.uk \
    /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).