unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: RE: Emacs pretest: highlight line number in display-line-numbers-mode?
Date: Fri, 20 Oct 2017 08:18:07 -0700 (PDT)	[thread overview]
Message-ID: <d1703253-afe6-4366-afff-ecfe87461a6a@default> (raw)
In-Reply-To: <<83376ee39c.fsf@gnu.org>>

> > >   . using a different face makes redisplay slightly slower
> > >     (because it disallows some redisplay optimizations)
> >
> > Would those optimizations still be available if a
> > user chose the same face for both (but the faces
> > were different by default)?

?

I guess you are confirming that the optimizations you
spoke of are a red herring here: they would anyway be
available whenever someone customizes the current-line
face to have the same appearance as the other-lines face.
Or do you want to correct this guess?

> > If so, I'd suggest making the faces different by
> > default.
> 
> They are already different by default.  They just have
> the same attributes.

I think you understood perfectly well that I was
referring to a difference of _appearance_, not the fact
that there are two different face objects.  There are
two faces, but they have the same appearance by default.
That's the misdesign.

Please consider giving them a different appearance by
default.  That will help users see which is the current
line, and it will help users know that there are two
different faces, which they can customize.

   If you think it is important, add a doc mention that if
   the faces have the same attribute values then display
   performance can be better.

> > IOW, opt-in for the loss of a difference.
> 
> That's already so.

No.  If the appearance is the same by default then
you have to opt out of that default behavior to see
a difference.  Lack of a difference in appearance
is not opt-in currently; it is the default behavior.



  parent reply	other threads:[~2017-10-20 15:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 15:19 Emacs pretest: highlight line number in display-line-numbers-mode? Sivaram Neelakantan
2017-10-19 15:37 ` Robert Pluim
2017-10-19 17:18   ` Drew Adams
2017-10-19 20:09     ` Eli Zaretskii
     [not found]     ` <<834lquew6p.fsf@gnu.org>
2017-10-19 20:43       ` Drew Adams
2017-10-20  6:34         ` Eli Zaretskii
2017-10-20 13:49           ` Robert Pluim
2017-10-20 14:49             ` Eli Zaretskii
     [not found]           ` <<87mv4mexpo.fsf@gmail.com>
     [not found]             ` <<83h8utdgcq.fsf@gnu.org>
2017-10-20 15:18               ` Drew Adams
2017-10-20 15:42                 ` Eli Zaretskii
     [not found]         ` <<83376ee39c.fsf@gnu.org>
2017-10-20 15:18           ` Drew Adams [this message]
2017-10-20 15:52             ` Eli Zaretskii
     [not found] <<krpqx3tvyv413v.fsf@gmail.com>
     [not found] <<<krpqx3tvyv413v.fsf@gmail.com>

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=d1703253-afe6-4366-afff-ecfe87461a6a@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).