From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: what is loading and when
Date: Tue, 06 Jun 2006 06:32:33 +0300 [thread overview]
Message-ID: <uhd2zyn5a.fsf@gnu.org> (raw)
In-Reply-To: <8764jfhzhh.fsf@newsguy.com> (reader@newsguy.com)
> From: reader@newsguy.com
> Date: Mon, 05 Jun 2006 19:58:02 -0500
>
> > Problems with CVS Emacs should be posted to emacs-devel@gnu.org.
>
> Hello Eli,
>
> I suspect it is more problem elsewhere in X or even in gentoo
> modifications so posted here.
Suit yourself, but even if these problems are with Gentoo, there's
much more expertise with the CVS code on emacs-devel than here.
> > Grepping the lisp tree for "no fonts matching" finds a single hit --
> > in fontset.el. Run fontset.el under Edebug or modify it to print some
> > useful info, and you should be able to find out who calls the function
> > that issues the warnings.
>
> I've renamed fontset.elc then edited fontset.el by commenting out the
> warning at line:406
> ;; (message "Warning: no fonts matching `%s' available" pattern)
>
> Starting a fresh emacs I still see the same warnings.
Of course, you would: fontset.elc is preloaded when Emacs is built, so
any changes in fontset.el that aren't followed by rebuilding Emacs
will have no effect.
next prev parent reply other threads:[~2006-06-06 3:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 11:27 what is loading and when reader
2006-06-05 19:54 ` Eli Zaretskii
2006-06-06 0:58 ` reader
2006-06-06 3:32 ` Eli Zaretskii [this message]
2006-06-07 10:20 ` reader
2006-06-07 15:24 ` Peter Dyballa
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=uhd2zyn5a.fsf@gnu.org \
--to=eliz@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.
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).