unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tumashu  <tumashu@163.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re:Re: face-remapping-alist can not override internal-border face?
Date: Sun, 10 Mar 2019 21:16:19 +0800 (CST)	[thread overview]
Message-ID: <4bdf73ce.63fe.16967bf39d1.Coremail.tumashu@163.com> (raw)
In-Reply-To: <8336nu7ulr.fsf@gnu.org>











At 2019-03-10 21:00:00, "Eli Zaretskii" <eliz@gnu.org> wrote:
>> Date: Sun, 10 Mar 2019 18:22:19 +0800 (CST)
>> From: tumashu  <tumashu@163.com>
>> Cc: "Eli Zaretskii" <eliz@gnu.org>, "emacs-devel@gnu.org" <emacs-devel@gnu.org>
>> I use below code to test, when child-frame is created, border's color is not 
>> change,  after I click frame with the help of mouse, the border's color change
>> to green
>> 
>>  
>>   (set-face-background
>>    'internal-border
>>    (face-attribute 'test :background)
>>    (make-frame `((internal-border-width . 100)
>> 		 (parent-frame . ,(window-frame)))))
>
>Try creating the frame first, and change the face only afterwards.

Thanks for your and martin's help, posframe can change border's color now:

   https://github.com/tumashu/posframe/commit/edfbff5ce5110e6d1a78bfe203fa8ec5d9d4e3ec

Now I need to do is deal with posframe's face-mapping argument, 
it use buffer-local face-mapping-alist,  a question is that:
Is there a function, which can replace a face's definition with other face's definition?

  reply	other threads:[~2019-03-10 13:16 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 [this message]
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=4bdf73ce.63fe.16967bf39d1.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).