From: Chong Yidong <cyd@gnu.org>
To: Left Right <olegsivokon@gmail.com>
Cc: 11850@debbugs.gnu.org,
"Yotam Medini יותם מדיני" <yotam.medini@gmail.com>
Subject: bug#11850: bug#11813: bug#11850: crash (null font) running emacs built from git
Date: Sun, 26 Aug 2012 12:36:31 +0800 [thread overview]
Message-ID: <874nnq46cw.fsf@gnu.org> (raw)
In-Reply-To: <CAJQBtgkGscrDXRCfOy3Hs_df44cXNyG1-4vBpgfLLscTVaP99g@mail.gmail.com> (Left Right's message of "Thu, 16 Aug 2012 13:51:19 +0300")
Left Right <olegsivokon@gmail.com> writes:
> Using the configuration option you suggested, I was prompted for
> missing library - tifflib. I've then installed tifflib5-dev from
> Debian. The configuration was successful afterwards.
> I attach the screenshot of how the version I compiled looks.
So now it looks like the default font displays fine, but your system has
problems displaying the bold font. That is a slightly different symptom
from what you had before. Please show the output of C-u C-x = for the
`bold' and `mode-line-buffer-id' faces. You can do this by typing
M-x describe-face- RET bold RET, moving the cursor to the text that says
"sample", and typing C-u C-x =. Similarly for `mode-line-buffer-id'.
I'm only interested in the part that reports the font. For sample, on
my machine it says
display: by this font (glyph code)
xft:-unknown-Droid Sans Mono-normal-normal-normal-*-13-*-*-*-m-0-iso10646-1 (#x56)
One possibility is that you have installed a buggy font which does not
include bold glyphs.
next prev parent reply other threads:[~2012-08-26 4:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 11:27 bug#11850: crash (null font) running emacs built from git Yotam Medini יותם מדיני
2012-07-03 16:35 ` Eli Zaretskii
2012-07-03 16:49 ` Eli Zaretskii
2012-07-04 14:31 ` Yotam Medini יותם מדיני
2012-07-04 16:32 ` Eli Zaretskii
2012-07-04 20:49 ` bug#11850: bug#11813: " Eli Zaretskii
2012-07-05 7:34 ` Left Right
2012-07-05 13:17 ` bug#11850: " Eli Zaretskii
2012-07-05 13:33 ` Left Right
2012-07-05 16:54 ` Eli Zaretskii
2012-07-07 22:42 ` Left Right
2012-07-07 22:58 ` bug#11850: " Left Right
2012-07-08 3:00 ` Eli Zaretskii
2012-07-08 14:20 ` Chong Yidong
2012-07-08 15:56 ` bug#11850: " Eli Zaretskii
2012-07-08 16:29 ` Left Right
2012-07-08 18:40 ` bug#11850: " Jan Djärv
2012-07-09 4:21 ` Chong Yidong
2012-07-11 17:36 ` Left Right
2012-07-12 7:18 ` Chong Yidong
2012-08-16 3:25 ` Chong Yidong
2012-08-16 10:51 ` bug#11813: " Left Right
2012-08-26 4:36 ` Chong Yidong [this message]
2012-09-19 13:01 ` Left Right
[not found] ` <CAAE-6rb+efByT+um7KB-MfvmN2QbOiq_GRRmuwN7drsDu8TC_A@mail.gmail.com>
[not found] ` <837guj4ffq.fsf@gnu.org>
2012-07-08 15:58 ` Yotam Medini יותם מדיני
2012-07-08 16:43 ` Eli Zaretskii
2012-07-03 17:15 ` Eli Zaretskii
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=874nnq46cw.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=11850@debbugs.gnu.org \
--cc=olegsivokon@gmail.com \
--cc=yotam.medini@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).