From: Robert Pluim <rpluim@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Identifying the face between STRETCH and right fringe.
Date: Tue, 27 Nov 2018 20:38:05 +0100 [thread overview]
Message-ID: <m2mupus44i.fsf@gmail.com> (raw)
In-Reply-To: <m2r2f6s589.fsf@gmail.com> (Robert Pluim's message of "Tue, 27 Nov 2018 20:14:14 +0100")
Robert Pluim <rpluim@gmail.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Robert Pluim <rpluim@gmail.com>
>>> Cc: emacs-devel@gnu.org
>>> Date: Tue, 27 Nov 2018 14:55:23 +0100
>>>
>>> >> When we get here, face->background == 1, and FRAME_BACKGROUND_PIXEL ==
>>> >> 0xfffeffff
>>> >>
>>> >> Looking through nsfns.m, the problem becomes obvious: the NS port uses
>>> >> indices into a color table to specify the background colour of faces,
>>> >> and FRAME_BACKGROUND_PIXEL is an RGBA value.
>>> >
>>> > Why does NS use indices here, and not RGBA values?
>>>
>>> Probably because NS doesnʼt really use the RGBA values directly at
>>> all, but uses the indices all the time.
>>
>> So where does the RGBA value in FRAME_BACKGROUND_PIXEL come from?
>>
>>> > If no better/cleaner idea emerges, how about having an NS-specific
>>> > code here that computed the it->face's background RGBA by indexing
>>> > into the color table, before comparing that with
>>> > FRAME_BACKGROUND_PIXEL?
(showing my ignorance of redisplay) Is there a reason we need to
compare with the background of the frame rather than with the
background of the default face of the frame?
Robert
next prev parent reply other threads:[~2018-11-27 19:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 16:39 Identifying the face between STRETCH and right fringe Keith David Bershatsky
2018-11-20 17:20 ` Eli Zaretskii
2018-11-21 7:44 ` Robert Pluim
2018-11-23 10:04 ` Eli Zaretskii
2018-11-23 13:25 ` Robert Pluim
2018-11-23 13:48 ` Eli Zaretskii
2018-11-23 14:04 ` Robert Pluim
2018-11-23 15:51 ` Eli Zaretskii
2018-11-23 15:58 ` Robert Pluim
2018-11-23 20:33 ` Eli Zaretskii
2018-11-27 8:56 ` Robert Pluim
2018-11-27 9:34 ` Eli Zaretskii
2018-11-27 11:02 ` Robert Pluim
2018-11-27 11:29 ` Eli Zaretskii
2018-11-27 13:55 ` Robert Pluim
2018-11-27 18:55 ` Eli Zaretskii
2018-11-27 19:14 ` Robert Pluim
2018-11-27 19:38 ` Robert Pluim [this message]
2018-11-28 6:03 ` Eli Zaretskii
2018-11-28 9:00 ` Robert Pluim
2018-11-28 9:42 ` Eli Zaretskii
2018-11-28 9:49 ` Eli Zaretskii
2018-11-28 13:24 ` Robert Pluim
2018-11-28 16:19 ` Eli Zaretskii
2018-11-28 7:13 ` Eli Zaretskii
2018-11-28 8:36 ` Robert Pluim
2018-11-28 9:45 ` Eli Zaretskii
2018-11-28 9:56 ` Robert Pluim
2018-11-28 10:11 ` Eli Zaretskii
2018-11-28 13:21 ` Robert Pluim
2018-11-28 16:20 ` Eli Zaretskii
2018-11-29 12:51 ` Robert Pluim
2018-11-29 14:15 ` Eli Zaretskii
2018-11-28 21:14 ` Alan Third
2018-11-29 12:26 ` Robert Pluim
2018-11-29 12:54 ` Eli Zaretskii
2018-11-29 13:52 ` Robert Pluim
2018-11-29 14:08 ` Eli Zaretskii
2018-11-30 7:59 ` Robert Pluim
2018-11-30 8:04 ` Robert Pluim
2018-11-30 8:22 ` Eli Zaretskii
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=m2mupus44i.fsf@gmail.com \
--to=rpluim@gmail.com \
--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 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).