From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 9648@debbugs.gnu.org
Subject: bug#9648: 24.0.90; popup-menu doesn't work on Lucid Emacs
Date: Mon, 03 Oct 2011 21:29:31 +0200 [thread overview]
Message-ID: <4E8A0D1B.4070104@swipnet.se> (raw)
In-Reply-To: <b4mlit215i9.fsf@jpl.org>
Hello.
The font Emacs chooses can be one of three:
If you have Xft (antialiased fonts) and one of Xsettings/Gsettings/GConf
it chooses the normal font for your desktop. You can see what it is by
calling the lisp function font-get-system-font.
Otherwise, it uses Sans-10 if you have Xft, or the default Xt font if not.
Jan D.
Katsumi Yamaoka skrev 2011-10-03 17:03:
> Katsumi Yamaoka<yamaoka@jpl.org> wrote:
>> Jan Djärv wrote:
>>> Katsumi Yamaoka skrev 2011-10-02 03:01:
>>>> (require 'gnus-art)
>>>> (popup-menu gnus-mime-button-menu)
>>>> I get a box that seems to be a menu but no text is displayed in it.
>
>> Uhm, I couldn't reproduce it today. The menu is displayed properly
>> with text. Now I'm in the office and use Emacs that I built Friday
>> on Cygwin under Windows XP. I'll try it again on Fedora 14 in home
>> about 14 hours later.
>
> I'm home. I verified it reproduces with the latest Emacs 24.0.90
> (I built it minutes ago) on Fedora 14. Here's a screenshot:
>
> http://www.jpl.org/tmp/Screenshot.png
>
> This happens with `emacs -Q', but setting the `Emacs*popup*font'
> resource with any font that provides ASCII characters solves it.
> Though it might not be an Emacs bug, I suspect there's something
> that leads Emacs to choose a wrong font when there's no X resource
> for `Emacs*popup*font'.
next prev parent reply other threads:[~2011-10-03 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 1:01 bug#9648: 24.0.90; popup-menu doesn't work on Lucid Emacs Katsumi Yamaoka
2011-10-02 2:40 ` Glenn Morris
2011-10-02 17:21 ` Jan Djärv
2011-10-03 0:31 ` Katsumi Yamaoka
2011-10-03 15:03 ` Katsumi Yamaoka
2011-10-03 19:29 ` Jan Djärv [this message]
2011-10-04 13:56 ` Katsumi Yamaoka
2022-01-27 17:52 ` Lars Ingebrigtsen
2022-01-27 22:46 ` Katsumi Yamaoka
2022-01-27 22:52 ` Lars Ingebrigtsen
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=4E8A0D1B.4070104@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=9648@debbugs.gnu.org \
--cc=yamaoka@jpl.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).