From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Chong Yidong <cyd@gnu.org>
Cc: 13278-done@debbugs.gnu.org
Subject: bug#13278: 24.3.50; Attributes aren't inherited in a copied face across frames
Date: Mon, 31 Dec 2012 09:16:31 +0900 [thread overview]
Message-ID: <b4md2xr13fk.fsf@jpl.org> (raw)
In-Reply-To: <b4m623pmv9j.fsf@jpl.org>
Chong Yidong <cyd@gnu.org> wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> Since at least 20.7, I verified. Perhaps is the present behavior
>> the spec?
> There is no "spec", but it's more or less expected behavior.
Ok. Though I cannot imagine using such a strange function usefully.
>>> Something to do with the FRAME argument of both these functions,
>>> I imagine.
>> So far I didn't find the way to make `my-bold' always bold by
>> fiddling them.
> May I ask why you are trying to use `copy-face' instead of `defface'?
I've been using it conveniently since the face feature was introduced
in Emacs. For example, it's handy when I want a face of which only
the color differs from the built-in one:
(copy-face 'bold 'orange-bold)
(set-face-foreground 'orange-bold "Orange")
Of course doing it by defface is not so troublesome, so I can live
without copy-face.
> As the docstring of `copy-face' indicates, it is mostly intended for
> internal usage,
Oh, I didn't notice the docstring having changed recently. I must
close this thread. Thanks anyway.
> and you are likely to screw up the face's customization
> data if you call it directly. If you give more details about the
> use-case, that would be good.
next prev parent reply other threads:[~2012-12-31 0:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 1:56 bug#13278: 24.3.50; Attributes aren't inherited in a copied face across frames Katsumi Yamaoka
2012-12-26 19:43 ` Glenn Morris
2012-12-30 1:28 ` Katsumi Yamaoka
2012-12-30 3:13 ` Chong Yidong
2012-12-31 0:16 ` Katsumi Yamaoka [this message]
2012-12-31 3:14 ` Drew Adams
2012-12-31 4:03 ` Chong Yidong
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=b4md2xr13fk.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=13278-done@debbugs.gnu.org \
--cc=cyd@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.