unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: A few faces.el questions
Date: Wed, 31 Jan 2007 19:07:45 -0500	[thread overview]
Message-ID: <E1HCPUP-0001TC-8o@fencepost.gnu.org> (raw)
In-Reply-To: <f7ccd24b0701310428s17056d64g98ff7fbb6e013a5b@mail.gmail.com> (lekktu@gmail.com)

    - The set-face-*-p family of functions all have an argument *-P (for
    example, INVERSE-VIDEO-P, BOLD-P, etc.). However, in the case of
    `set-face-underline-p' this is misleading, because UNDERLINE-P is not
    a flag (it can also be a color). Will someone object if I just change
    arg UNDERLINE-P to UNDERLINE and fix the info in the Emacs Lisp
    Reference (which doesn't mention the color option)? (This would also
    affect `modify-face', BTW.)

This function has been around for a long time, so let's not think of
changing its name now.

    - I know `internal-find-face' and `internal-get-face' are obsolete
    since 21.1, but their docstrings lie horribly about the FRAME
    argument. Wouldn't be better to just say "The argument FRAME is
    ignored"?

Ok.

    - Shouldn't `face-id' return an answer also for face aliases? I.e., instead of

In principle, that sounds right, but I don't want to risk the change now.

    - `face-differs-from-default-p' checks all face attributes except
    :inherit (obviously) and :stipple. Should it check :stipple?

Yes, if there is really a bug.  Can you verify that there is one?

  parent reply	other threads:[~2007-02-01  0:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 12:28 A few faces.el questions Juanma Barranquero
2007-01-31 18:43 ` Eli Zaretskii
2007-01-31 19:35   ` Drew Adams
2007-01-31 19:55     ` Juanma Barranquero
2007-02-01 16:19     ` Richard Stallman
2007-02-01  0:07 ` Richard Stallman [this message]
2007-02-01  0:27   ` Juanma Barranquero
2007-02-02 11:24     ` Richard Stallman

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=E1HCPUP-0001TC-8o@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.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).