unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tumashu  <tumashu@163.com>
To: "martin rudalics" <rudalics@gmx.at>
Cc: Eli Zaretskii <eliz@gnu.org>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re:Re: face-remapping-alist can not override internal-border face?
Date: Sat, 9 Mar 2019 22:28:32 +0800 (CST)	[thread overview]
Message-ID: <376d7fef.5d24.16962dafb01.Coremail.tumashu@163.com> (raw)
In-Reply-To: <5C82B9FC.3090505@gmx.at>











At 2019-03-09 02:52:44, "martin rudalics" <rudalics@gmx.at> wrote:
> > Sorry, I do not understand this,  does this mean: test is inherited to default face,
> > so internal-border is remapped to default instead of test? but the below code
> > seem to not work too:
> >
> > (defface test
> >    '((:background "green"))
> >    "Face used by the ivy-posframe."
> >    :group 'ivy-posframe)
> >
> > (setq face-remapping-alist '((internal-border . test)))
> >
> > (make-frame '((internal-border-width . 100)))
> >
> > (redraw-display)
>
>In a package I wrote I added a separate 'defcustom' to let users
>specify the background of the internal border like
>
>(defcustom my-internal-border "blue"
>   "Background of internal border."
>   :type 'string
>   ...)
>
>and later use
>
>(set-face-background 'internal-border my-internal-border ...)
>
>to put that into effect.  I don't recall whether I then conducted
>special experiments as to whether other solutions would work but
>faintly recall that the face of the internal border is special in a
>way.

I think set-face-background will change internal-border globally,
Do we have any method which can let differnet frame have different border color?
>
>martin

  reply	other threads:[~2019-03-09 14:28 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 [this message]
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

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=376d7fef.5d24.16962dafb01.Coremail.tumashu@163.com \
    --to=tumashu@163.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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).