unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Identifying the face between STRETCH and right fringe.
Date: Wed, 28 Nov 2018 14:24:59 +0100	[thread overview]
Message-ID: <m2lg5dbahg.fsf@gmail.com> (raw)
In-Reply-To: <837egxfs59.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 28 Nov 2018 11:49:54 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Wed, 28 Nov 2018 11:42:40 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: emacs-devel@gnu.org
>> 
>> > From: Robert Pluim <rpluim@gmail.com>
>> > Cc: emacs-devel@gnu.org
>> > Date: Wed, 28 Nov 2018 10:00:53 +0100
>> > 
>> > In this particular case extend_face_to_end_of_line has already done:
>> > 
>> >   default_face =
>> >     FACE_FROM_ID_OR_NULL (f, lookup_basic_face (it->w, f, DEFAULT_FACE_ID));
>> > 
>> > so there'd be no additional cost
>> 
>> Yes, but this part could (and probably should) be moved to after the
>> 'return', because default_face is not used before that.
>
> And btw, when the default face is remapped, its background color no
> longer has to be the same as the frame's background, right?  Which I
> guess is another reason why we use FRAME_BACKGROUND_PIXEL there.

OK, we can stick with that if no other proposals come up.

Moving the default_face lookup down in the function I can test for a
while. Iʼll even remove the _OR_NULL, since we donʼt check for NULL
anywhere anyway.

Robert



  reply	other threads:[~2018-11-28 13:24 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
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 [this message]
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=m2lg5dbahg.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --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).