From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>, tumashu <tumashu@163.com>
Cc: emacs-devel@gnu.org
Subject: Re: face-remapping-alist can not override internal-border face?
Date: Sun, 10 Mar 2019 14:35:53 +0100 [thread overview]
Message-ID: <5C8512B9.4010404@gmx.at> (raw)
In-Reply-To: <835zsq7v5u.fsf@gnu.org>
> Buffer-local variables that determine frame-global behavior are a bad
> idea.
Yes. I would use the term "frame-local" here. Framewise
specification should be done with frame parameters.
> Don't be surprised if you will see the face change unexpectedly
> because some other buffer happened to be the current buffer when the
> border was redrawn.
Buffer-local values should be used for buffers and windows only. As
for the latter, window parameters are useful when specifying something
that should survive showing another buffer in that window.
martin
prev parent reply other threads:[~2019-03-10 13:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 4:30 face-remapping-alist can not override internal-border face? tumashu
2019-03-08 8:26 ` Eli Zaretskii
2019-03-08 16:19 ` tumashu
2019-03-08 18:52 ` martin rudalics
2019-03-09 14:28 ` tumashu
2019-03-09 14:55 ` Eli Zaretskii
2019-03-10 0:35 ` tumashu
2019-03-10 3:36 ` Eli Zaretskii
2019-03-10 8:47 ` martin rudalics
2019-03-10 10:22 ` tumashu
2019-03-10 10:28 ` tumashu
2019-03-10 13:00 ` Eli Zaretskii
2019-03-10 13:16 ` tumashu
2019-03-10 13:44 ` Eli Zaretskii
2019-03-11 13:32 ` tumashu
2019-03-11 15:11 ` Eli Zaretskii
2019-03-10 12:45 ` Eli Zaretskii
2019-03-10 12:39 ` Eli Zaretskii
2019-03-10 13:04 ` tumashu
2019-03-10 13:41 ` Eli Zaretskii
2019-03-10 8:45 ` martin rudalics
2019-03-09 17:16 ` Eli Zaretskii
2019-03-09 17:51 ` Eli Zaretskii
2019-03-10 10:14 ` tumashu
2019-03-10 12:47 ` Eli Zaretskii
2019-03-10 13:35 ` martin rudalics [this message]
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=5C8512B9.4010404@gmx.at \
--to=rudalics@gmx.at \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tumashu@163.com \
/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).