From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: larsi@gnus.org, 53636@debbugs.gnu.org, tsdh@gnu.org
Subject: bug#53636: 29.0.50; face-remapping broken on master
Date: Tue, 08 Feb 2022 20:57:28 +0200 [thread overview]
Message-ID: <835yppw5if.fsf@gnu.org> (raw)
In-Reply-To: <517f576b-6a6b-3e1e-b899-b67bcf9ad512@gmx.at> (message from martin rudalics on Tue, 8 Feb 2022 19:24:19 +0100)
> Date: Tue, 8 Feb 2022 19:24:19 +0100
> Cc: larsi@gnus.org, 53636@debbugs.gnu.org, tsdh@gnu.org
> From: martin rudalics <rudalics@gmx.at>
>
> >> Face remapping has never been properly synchronized with windows and
> >> frames. What's needed is a simple hierarchy window > window's buffer >
> >> window's frame where the first should be implemented with the help of a
> >> 'face-remapping' window parameter and the last with the help of a
> >> 'face-remapping' frame parameter. Just like we (should) do for things
> >> like the scroll bars or fringes. But we need a consensus on this first.
> >
> > I don't think I understand this remark. While what you describe might
> > be a useful addition, I don't see why we must have it, or else.
> > Surely, Emacs has gobs of features that depend only on the buffer, but
> > not on the window nor the frame where that buffer is displayed? Why
> > cannot we have a reasonable behavior with face-remapping-alist being
> > specific to a buffer, no matter in what window we display it?
>
> What makes you think that this is not part of my proposal? What I mean
> is to have a clear rule how, for example, a buffer local setting of
> 'face-remapping-alist' may affect the creation of a new frame and the
> display of buffers in it.
OK, then we need first to agree on what is the reasonable expected
behavior in such cases.
next prev parent reply other threads:[~2022-02-08 18:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 13:52 bug#53636: 29.0.50; face-remapping broken on master Tassilo Horn
2022-01-30 17:41 ` Lars Ingebrigtsen
2022-01-30 18:27 ` Eli Zaretskii
2022-01-30 18:31 ` Lars Ingebrigtsen
2022-01-30 19:19 ` Eli Zaretskii
2022-01-30 20:25 ` Eli Zaretskii
2022-01-30 20:28 ` Lars Ingebrigtsen
2022-01-31 12:20 ` Eli Zaretskii
2022-01-31 19:44 ` Eli Zaretskii
2022-02-01 19:38 ` Lars Ingebrigtsen
2022-02-01 20:09 ` Eli Zaretskii
2022-02-02 17:59 ` Lars Ingebrigtsen
2022-02-02 18:07 ` Eli Zaretskii
2022-02-02 19:48 ` Lars Ingebrigtsen
2022-02-02 21:12 ` bug#53636: [External] : " Drew Adams
2022-02-03 6:53 ` Eli Zaretskii
2022-02-03 19:24 ` Lars Ingebrigtsen
2022-02-03 19:53 ` Eli Zaretskii
2022-02-05 6:20 ` Lars Ingebrigtsen
2022-02-05 7:50 ` Eli Zaretskii
2022-02-05 16:14 ` bug#53636: [External] : " Drew Adams
2022-02-05 22:27 ` Lars Ingebrigtsen
2022-02-06 7:12 ` Eli Zaretskii
2022-02-06 23:16 ` Lars Ingebrigtsen
2022-02-07 15:03 ` Eli Zaretskii
2022-02-08 6:08 ` Lars Ingebrigtsen
2022-02-08 8:58 ` martin rudalics
2022-02-08 12:41 ` Eli Zaretskii
2022-02-08 18:24 ` martin rudalics
2022-02-08 18:57 ` Eli Zaretskii [this message]
2022-02-08 12:29 ` Eli Zaretskii
2022-02-09 8:01 ` Lars Ingebrigtsen
2022-02-09 13:57 ` Eli Zaretskii
2022-02-12 12:20 ` Eli Zaretskii
2022-02-13 8:20 ` Lars Ingebrigtsen
2022-02-13 8:31 ` Tassilo Horn
2022-02-15 9:31 ` Tassilo Horn
2022-02-13 11:58 ` Eli Zaretskii
2022-02-14 10:38 ` Lars Ingebrigtsen
2022-02-03 18:30 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835yppw5if.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53636@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rudalics@gmx.at \
--cc=tsdh@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.