unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Subject: Who can explain the display architecture?
Date: Thu, 14 Jul 2005 14:55:01 -0400	[thread overview]
Message-ID: <uhdexqku2.fsf_-_@boost-consulting.com> (raw)
In-Reply-To: ull57tgjt.fsf_-_@boost-consulting.com


I am trying to get a clue as to how this stuff is organized so that I
can fix the problems described below.  Thanks for your attention.

David Abrahams <dave@boost-consulting.com> writes:

> This concerns the one remaining problem with the ClearType patch I'm
> trying to clean up and submit.  I hope I don't seem too insistent, but
> I've been trying to get a hint for about a week.
>
> David Abrahams <dave@boost-consulting.com> writes:
>
>> David Abrahams <dave@boost-consulting.com> writes:
>>
>>> David Abrahams <dave@boost-consulting.com> writes:
>>>
>>>> I am seeing some minor artifacts that I don't know what to do about.
>>>> For example, when I backspace over these parens starting from the end
>>>> of the line, I end up with some small remnants of the background color
>>>> emacs uses to highlight matching parens for me.  When all the close
>>>> parens are gone there's a thin vertical cyan line at the right edge of
>>>> each open paren.  Any clues where to attack that?
>>>>
>>>> ((((()))))
>>>
>>> Even some vague hints would be a big help here.  This is the only
>>> remaining detail as far as I can tell.
>>
>> I have one more piece of information for anyone who can think about
>> this problem for a moment: When I do `C-s x', the first instance of x
>> (or whatever character) that is found gets highlighted in purple and
>> looks right.  The next instance of x on that line gets highlighted in
>> cyan and looks right.  The rest of the instances of x on that line get
>> highlighted in cyan, and the highlighting extends one pixel too far to
>> the left.  On each line thereafter, the first instance of x is
>> highlighted in cyan and looks right, and the rest of the instances on
>> that line are highlighted in cyan and look wrong (i.e. the
>> highlighting extends one pixel too far to the left).
>
> Can someone please give me some hint as to which entry points to
> breakpoint in order to observe these calculations and/or drawing in
> action?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

  reply	other threads:[~2005-07-14 18:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 12:38 Emacs defeats ClearType David Abrahams
2005-06-03  8:30 ` jasonr
2005-06-03 10:54   ` David Abrahams
2005-06-03 15:22     ` jasonr
2005-06-03 15:27   ` David Abrahams
2005-06-06 15:47     ` jasonr
2005-06-06 16:46       ` David Abrahams
2005-06-07  1:15         ` Miles Bader
2005-06-07 13:20           ` David Abrahams
2005-06-08 13:45         ` [PING] ClearType Patch David Abrahams
2005-06-08 14:33           ` Eli Zaretskii
2005-06-08 15:46             ` David Abrahams
2005-06-08 16:44               ` Stefan Monnier
2005-06-08 20:01                 ` David Abrahams
2005-06-08 18:22               ` Eli Zaretskii
2005-06-08 19:57                 ` David Abrahams
2005-06-08 21:29                   ` jasonr
2005-06-08 21:23                 ` jasonr
2005-06-08 22:17                   ` David Abrahams
2005-06-09  8:10                     ` jasonr
2005-06-11 13:12                       ` Eli Zaretskii
2005-06-11 16:50                         ` David Abrahams
2005-06-15  7:15                           ` David Abrahams
2005-06-15  9:19                             ` David Abrahams
2005-06-18 23:02                               ` How is highlighting done in show-paren-mode? David Abrahams
2005-07-14 18:55                                 ` David Abrahams [this message]
2005-07-15  9:41                                   ` Who can explain the display architecture? Kim F. Storm
2005-06-08 23:34                   ` [PING] ClearType Patch Stefan Monnier

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=uhdexqku2.fsf_-_@boost-consulting.com \
    --to=dave@boost-consulting.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 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).