unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: manuel@ledu-giraud.fr,  emacs-devel@gnu.org
Subject: Re: [PATCH] Fix placement of toggle and radio button in Lucid menu.
Date: Sat, 26 Feb 2022 15:33:40 +0800	[thread overview]
Message-ID: <874k4m5bfv.fsf@yahoo.com> (raw)
In-Reply-To: <83tucmp2lp.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 26 Feb 2022 08:24:18 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> Sorry, I don't understand how this is relevant.

The problem is that the Lucid menu bar widget doesn't find fonts like
the rest of Emacs does, using the individual font backends.  Instead, it
relies on various ad hoc methods for font discovery that change
depending on how it is built.  I didn't look too closely, but font
metrics are probably calculated differently as well.

But I thought you were suggesting that the Lucid menu bar widget used
font objects opened by Emacs.

> What I meant is to invoke Emacs like this:
>
>    emacs -Q -fn SOMETHING
>
> where SOMETHING is the font used in the Lucid menus, and the examine
> the metrics of the relevant characters and of the font inside
> gui_produce_glyphs.
>
> The only difficulty I could see is if somehow it is not easy to know
> which font is used in the Lucid menus.  Is that the problem?

That's also a problem, but you can control the font by starting Emacs
with "-xrm 'Emacs.pane.menubar.font: Courier-12''" or something to that
effect.  But keep in mind that the metrics may still be different, due
to the aformentioned caveats.  For instance, it might elect to use X
server-side fonts even if the same font is displayed using Xft by the
rest of Emacs, very often resulting in different metrics.

Thanks.



  reply	other threads:[~2022-02-26  7:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  9:01 [PATCH] Fix placement of toggle and radio button in Lucid menu Manuel Giraud
2022-02-24 10:06 ` Po Lu
2022-02-24 10:19   ` Po Lu
2022-02-24 10:36     ` Eli Zaretskii
2022-02-24 14:09     ` Manuel Giraud
2022-02-25 11:16     ` Manuel Giraud
2022-02-25 11:50       ` Po Lu
2022-02-26 17:38         ` Manuel Giraud
2022-02-25 12:18       ` Eli Zaretskii
2022-02-25 12:52         ` Manuel Giraud
2022-02-25 13:05           ` Eli Zaretskii
2022-02-25 13:46             ` Po Lu
2022-02-25 14:10               ` Eli Zaretskii
2022-02-26  0:20                 ` Po Lu
2022-02-26  6:24                   ` Eli Zaretskii
2022-02-26  7:33                     ` Po Lu [this message]
2022-02-26  7:51                       ` Eli Zaretskii
2022-02-26  8:35                         ` Po Lu
2022-02-26  8:53                           ` Eli Zaretskii
2022-02-25 14:46             ` Manuel Giraud
2022-02-25 14:57               ` Eli Zaretskii
2022-02-25 15:38                 ` Manuel Giraud
2022-02-25 16:35                   ` Eli Zaretskii
2022-02-26  0:21                     ` Po Lu
2022-02-26  6:26                       ` Eli Zaretskii
2022-02-26  7:35                         ` Po Lu
2022-02-28  8:45                           ` Manuel Giraud
2022-02-28 13:21                             ` Eli Zaretskii
2022-02-28 21:19                               ` Manuel Giraud
2022-03-01  3:33                                 ` Eli Zaretskii
2022-03-02 12:06                                   ` Manuel Giraud
2022-02-28 18:35                             ` chad
2022-03-02 12:10                               ` Manuel Giraud

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=874k4m5bfv.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    /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).