unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
	emacs-devel@gnu.org, Brian Palmer <bpalmer@rescomp.stanford.edu>,
	xemacs-beta@xemacs.org
Subject: Re: intern-soft, find-face/get-face, and facep for determining faces' definedness
Date: Tue, 02 Nov 2004 18:50:53 +0900	[thread overview]
Message-ID: <buozn20y3ya.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <847aaaf20411020121678a0b5c@mail.gmail.com> (Brian Palmer's message of "Tue, 2 Nov 2004 02:21:10 -0700")

Brian Palmer <bpalmer@gmail.com> writes:
>> Given that Xemacs has a differing definition of facep requiring one to
>> use `find-face' instead, would an Emacs version:
>> 
>>    (defun find-face (face) (and (facep face) face))
>> 
>> do the job?
>
> I think so, as long as emacs allows a face-name everywhere a face is 
> permitted.

For most purposes, Emacs doesn't have a special face type, it only has
face-names.

It's also possible to get a lisp vector containing face attributes, but
this is typically only useful for a few special tasks -- most interfaces
want a face-name).

To be reasonably compatible with Xemacs, it would be necessary to know
what exactly a face-object (such as returned by `find-face') is useful
for, and I don't.  But my guess is that a face-name is closer than a
face-vector.

-Miles
-- 
Saa, shall we dance?  (from a dance-class advertisement)

  reply	other threads:[~2004-11-02  9:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-01 21:40 intern-soft, find-face/get-face, and facep for determining faces' definedness Brian Palmer
2004-11-02  6:14 ` Stephen J. Turnbull
2004-11-02  7:28   ` Brian Palmer
2004-11-02  7:45     ` Miles Bader
2004-11-02  8:48       ` Brian Palmer
2004-11-02  9:08         ` Miles Bader
2004-11-02  9:21           ` Brian Palmer
2004-11-02  9:50             ` Miles Bader [this message]
2004-11-02 12:06               ` Stephen J. Turnbull
2004-11-02 22:20                 ` Miles Bader
2004-11-06  9:31                   ` Oliver Scholz
2004-11-02 11:07           ` Stephen J. Turnbull
2004-11-02 12:01             ` Stefan
2004-11-02 22:23               ` Miles Bader
2004-11-03 12:45               ` Richard Stallman
2004-11-03 14:15                 ` Stefan Monnier
2004-11-03 15:01                   ` Zajcev Evgeny
2004-11-03 15:20                     ` Andreas Schwab
2004-11-03 15:54                       ` Zajcev Evgeny
2004-11-04  9:28                         ` Stephen J. Turnbull
2004-11-03 15:48                     ` Stefan Monnier
2004-11-04  3:41               ` Stephen J. Turnbull
2004-11-05  7:55                 ` Stefan
2004-11-09 14:41                   ` Stephen J. Turnbull

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=buozn20y3ya.fsf@mctpc71.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=bpalmer@rescomp.stanford.edu \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=stephen@xemacs.org \
    --cc=xemacs-beta@xemacs.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 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).