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 15:01:20 +0300 [thread overview]
Message-ID: <83d0er62y7.fsf@gnu.org> (raw)
In-Reply-To: <87blubfxq9.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 20 Oct 2019 13:43:58 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: all_but_last@163.com, 37829@debbugs.gnu.org
> Date: Sun, 20 Oct 2019 13:43:58 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > And doing this the opposite way makes no sense to me, it's in effect
> > the same as removing the feature.
>
> I don't understand. Doing it the opposite way would be just as
> expressive.
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.
> > > This change breaks a lot of out-of-tree code.
> >
> > No, it doesn't break any code. It changes how display looks in some
> > cases, so people are surprised at first.
>
> You may quibble, but changing the look this radically is breaking the
> code for me.
I suggest to run with it for some time, you may change your mind. It
happened to many of us.
> > For this particular bug report, why would someone expect the overlay's
> > color to extend to the end of the line instead of affecting only the
> > text that the overlay covers?
>
> Because that's the way Emacs has worked since forever: If you put a face
> on a newline, then it'll extend to the end of the line.
We considered that a side effect of the implementation. Many other
applications don't do that.
> 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. 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).
next prev parent reply other threads:[~2019-10-20 12:01 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 [this message]
2019-10-20 16:49 ` Lars Ingebrigtsen
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=83d0er62y7.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 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.