unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: An unwonted warning I constantly get about fontsets when I start Emacs
Date: Sat, 27 May 2017 17:09:25 +0300	[thread overview]
Message-ID: <83r2zagzmy.fsf@gnu.org> (raw)
In-Reply-To: <ygm8tli5s99.fsf@xi> (message from Göktuğ Kayaalp on Sat, 27 May 2017 16:44:18 +0300)

> From: Göktuğ Kayaalp <self@gkayaalp.com>
> Cc: help-gnu-emacs@gnu.org
> Date: Sat, 27 May 2017 16:44:18 +0300
> 
> >> >> Error (initialization): Creation of the default fontsets failed:
> >> >> (error Invalid script or charset name: old-italic)
> >> >>
> >> >> [...]
> >> > Please show your fontset-related customizations.
> >> 
> >> I don't have any such customisations in Emacs.  Just setting the font
> >> for some faces here and there:
> >
> > Strange, I don't see old-italic mentioned anywhere.
> >
> > Are you sure you don't have some stale Lisp files lying around and
> > shadowing the ones which come with the distribution?
> 
> None of my lisp files contain the word `fontset'.  I've looked quite a
> bit, but haven't found anything related.  I just learnt what it is,
> actually.
> 
> > Also, do you see this problem with "emacs -Q"?
> 
> Yes.  The message comes up in the *Warnings* buffer with or without -Q.
> No problems with any functionality so far tho, just the warning.

This becomes more and more stuff for a bug report, not for discussion
here.

The old-italic script is defined in charscript.el, so check that file
for problems (damaged, truncated, outdated).  It is then used in
fontset.el, and the error you see comes from there, see the function
create-default-fontset.  Maybe by looking into these two files, or by
searching your system for outdated versions which shadow these, you
will find the culprit.

My next suggestion is to make sure the tree where you build Emacs is
clean, and doesn't contain any stale files from the previous versions
you've built.



  reply	other threads:[~2017-05-27 14:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-27  9:22 An unwonted warning I constantly get about fontsets when I start Emacs Göktuğ Kayaalp
2017-05-27  9:42 ` Eli Zaretskii
2017-05-27 11:52   ` Göktuğ Kayaalp
2017-05-27 13:37     ` Eli Zaretskii
2017-05-27 13:44       ` Göktuğ Kayaalp
2017-05-27 14:09         ` Eli Zaretskii [this message]
2017-05-27 22:27           ` Göktuğ Kayaalp
2017-05-28  4:15             ` Eli Zaretskii
2017-05-28  4:33               ` Eli Zaretskii
2017-05-28  7:56                 ` tomas
2017-05-28 15:01                   ` Eli Zaretskii
2017-05-28 13:14                 ` Göktuğ Kayaalp
2017-05-28 14:32                   ` Göktuğ Kayaalp
2017-05-28 15:41                     ` Eli Zaretskii
2017-05-28 18:14                       ` Göktuğ Kayaalp
2017-05-28 13:16               ` Göktuğ Kayaalp
  -- strict thread matches above, loose matches on Subject: below --
2017-05-27  9:25 Göktuğ Kayaalp

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=83r2zagzmy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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).