unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 37829@debbugs.gnu.org, all_but_last@163.com
Subject: bug#37829: 27.0.50; Overlay behaviour changed without documentation.
Date: Sun, 20 Oct 2019 22:13:41 +0300	[thread overview]
Message-ID: <83o8yb44d6.fsf@gnu.org> (raw)
In-Reply-To: <87ftjne50s.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  20 Oct 2019 18:49:23 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: all_but_last@163.com,  37829@debbugs.gnu.org
> Date: Sun, 20 Oct 2019 18:49:23 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > The idea behind this feature was that most faces shall not be
> > extended, so doing it the opposite way would mean we need to change
> > the definitions of an unlimited number of faces, including those not
> > in core.
> 
> We do not have to change anything not in core -- whether people want the
> new, more convenient behaviour, is up to them.

But under the assumption that most faces should not be extended, that
would mean our default is wrong in most cases, and what kind of
default is that?

> And there certainly aren't unlimited places we have to change thing
> in-tree, because most things in-tree look just how we wanted them to.

I said "including those not in core".

> > Others said the exact opposite: that they want to be able to do that
> > without having the face extended.
> 
> With the new interface, they can do that, whatever the default is.

They wanted to do that without customizing the faces.

> > Also, the automatic extension in Emacs 26 and before behaved
> > inconsistently in GUI and text-mode frames, and even between different
> > attributes (color vs underline, for example).
> 
> Well, the only attributes where it makes a difference are background
> colours and underline, surely?  (Well, and overline, but nobody uses
> that.)

No, there's also strikethrough and box.





  reply	other threads:[~2019-10-20 19:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-20  8:49 bug#37829: 27.0.50; Overlay behaviour changed without documentation Zhu Zihao
2019-10-20 11:05 ` Eli Zaretskii
2019-10-20 11:16   ` Lars Ingebrigtsen
2019-10-20 11:35     ` Eli Zaretskii
2019-10-20 11:43       ` Lars Ingebrigtsen
2019-10-20 12:01         ` Eli Zaretskii
2019-10-20 16:49           ` Lars Ingebrigtsen
2019-10-20 19:13             ` Eli Zaretskii [this message]
2019-10-21 19:43               ` Lars Ingebrigtsen
2019-10-20 11:31   ` Zhu Zihao
2019-10-20 16:14   ` Zhu Zihao
2019-10-20 19:15     ` Eli Zaretskii
2020-08-21 15:03   ` Lars Ingebrigtsen

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=83o8yb44d6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37829@debbugs.gnu.org \
    --cc=all_but_last@163.com \
    --cc=larsi@gnus.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).