Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@hardakers.net>
Subject: Re: um, highlighting/fonts/something broken in CVS?
Date: Mon, 22 Dec 2003 11:17:24 -0800	[thread overview]
Message-ID: <sdhdzsek6z.fsf@wanderer.hardakers.net> (raw)
In-Reply-To: <sd8yl4668x.fsf@wanderer.hardakers.net> (Wes Hardaker's message of "Mon, 22 Dec 2003 10:45:50 -0800")

>>>>> On Mon, 22 Dec 2003 10:45:50 -0800, Wes Hardaker <wes@hardakers.net> said:

Wes> So, I updated gnus a few days ago and now my gnus-highlight
Wes> package doesn't work anymore and it's possible other fonts are
Wes> messed up as well (but I'm still looking for a definite answer on
Wes> that).  It seems that custom-declare-face now, um, isn't?

Odd...  facep seems to return nil for symbols now.  I don't get how
this could have changed by updating gnus, but that's all I did.  Very
weird.

Anyway, I fixed my code at least by no longer testing to see if the
symbol is a valid face.  This doesn't seem wise, but I guess now errors
in a font specification will cause real errors (as opposed to
previously being ignored).

This works:

  (facep (get-face 'highlight))

But of course, you'd have to trap the error now that get-face would
throw if highlight wasn't define.

-- 
"In the bathtub of history the truth is harder to hold than the soap,
 and much more difficult to find."  -- Terry Pratchett



  reply	other threads:[~2003-12-22 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-22 18:45 Wes Hardaker
2003-12-22 19:17 ` Wes Hardaker [this message]
2003-12-22 20:18   ` Jesper Harder
2003-12-22 23:13 ` Xavier Maillard

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=sdhdzsek6z.fsf@wanderer.hardakers.net \
    --to=wes@hardakers.net \
    /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.
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 NNTP newsgroup(s).