From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.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 18:49:23 +0200 [thread overview]
Message-ID: <87ftjne50s.fsf@gnus.org> (raw)
In-Reply-To: <83d0er62y7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Oct 2019 15:01:20 +0300")
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.
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 suggest to run with it for some time, you may change your mind. It
> happened to many of us.
I know that the new interface is convenient -- I'll be able to ditch a
bunch of code in shr that works around the problem. But that's just
it -- this is what everybody has done forever, and have ended up with
code that does exactly what they want it to. (I.e., placing a face on
newline to extend the face to the end of the line.)
>> We do that because that's the way we wanted the display to look. If we
>> didn't want that, we didn't put the face on the newline.
>
> 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. The
question is whether Emacs should do this massive, extremely user-visible
(with very ugly results) thing by default.
I think no.
> 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.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-20 16:49 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 [this message]
2019-10-20 19:13 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftjne50s.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37829@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.