unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: David Ponce <da_vid@orange.fr>
Cc: luangruo@yahoo.com, 57652@debbugs.gnu.org, gregory@heytings.org
Subject: bug#57652: 29.0.50; Warning setting attribute of face ‘term’
Date: Thu, 08 Sep 2022 11:42:38 +0300	[thread overview]
Message-ID: <83czc6fe9t.fsf@gnu.org> (raw)
In-Reply-To: <319e3926-7c22-cabd-43dd-a02f3a01c734@orange.fr> (message from David Ponce on Thu, 8 Sep 2022 10:22:31 +0200)

> Cc: 57652@debbugs.gnu.org, gregory@heytings.org
> Date: Thu, 8 Sep 2022 10:22:31 +0200
> From: David Ponce <da_vid@orange.fr>
> 
>     "Apart from the values given below, each face attribute can have the
> value ‘unspecified’.  This special value means that the face doesn’t
> specify that attribute directly.  An ‘unspecified’ attribute tells Emacs
> to refer instead to a parent face (see the description ‘:inherit’
> attribute below); or, failing that, to an underlying face (*note
> Displaying Faces::).  (However, ‘unspecified’ is not a valid value in
> ‘defface’.)"
> 
> So it seems that unspecified is not allowed in defface.

Where does it say that unspecified is not allowed?  (And this doc
string is from set-face-attribute, not from defface.)

> So, how to specify a missing attribute excepted by using nil in the
> defface used in term.el?

If you don't have anything to say about an attribute, just don't
mention it in defface.  That's what unspecified means, as the doc
string says.  So I'm unsure why you would need "to specify a missing
attribute".





  reply	other threads:[~2022-09-08  8:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 18:49 bug#57652: 29.0.50; Warning setting attribute of face ‘term’ David Ponce
2022-09-08  5:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-08  8:22   ` David Ponce
2022-09-08  8:42     ` Eli Zaretskii [this message]
2022-09-08 12:34       ` David Ponce
2022-09-08  8:43     ` David Ponce
2022-09-08 11:44     ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=83czc6fe9t.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57652@debbugs.gnu.org \
    --cc=da_vid@orange.fr \
    --cc=gregory@heytings.org \
    --cc=luangruo@yahoo.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).