unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: 64270@debbugs.gnu.org
Subject: bug#64270: 30.0.50; Font update for no toolkit menu
Date: Tue, 27 Jun 2023 21:18:23 +0300	[thread overview]
Message-ID: <83v8f8vkeo.fsf@gnu.org> (raw)
In-Reply-To: <87sfacubwa.fsf@ledu-giraud.fr> (message from Manuel Giraud on Tue, 27 Jun 2023 18:07:33 +0200)

> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: 64270@debbugs.gnu.org
> Date: Tue, 27 Jun 2023 18:07:33 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Manuel Giraud <manuel@ledu-giraud.fr>
> >> Cc: 64270@debbugs.gnu.org
> >> Date: Tue, 27 Jun 2023 16:13:15 +0200
> >> 
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >> 
> >> > If this is not what you meant, then how would Emacs know which font to
> >> > select for menus when the default face's font is changed?
> >> 
> >> For my usage, I imagine that yes the menu font would change when I
> >> change the frame's default face.  But this because my menu face is
> >> already derived from the default face.
> >> 
> >> For the general usage, my idea (and what I start doing in my patch, see
> >> my first message) is to query the MENU_FACE_ID.  So the font into the
> >> menus would change if the user modify its menu face.
> >
> > This is a misunderstanding: I didn't ask what would be the trigger to
> > change the font.  I asked how would Emacs know _which_ font to choose
> > for the menus?
> 
> I also am not sure I understand.  I don't think that Emacs has to choose
> a font here.  It would use the font used for the menu face.  What am I
> missing?

How is this different from what happens today?





  reply	other threads:[~2023-06-27 18:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 17:00 bug#64270: 30.0.50; Font update for no toolkit menu Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-24 17:16 ` Eli Zaretskii
2023-06-27  7:04   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 11:26     ` Eli Zaretskii
2023-06-27 14:13       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 15:54         ` Eli Zaretskii
2023-06-27 16:07           ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 18:18             ` Eli Zaretskii [this message]
2023-06-28  0:28               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-28  7:50                 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-28  9:20                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-28  7:38               ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-25  0:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  7:08   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  7:48     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  8:25       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  8:37       ` Robert Pluim
2023-06-27  8:47         ` Robert Pluim
2023-06-27  8:55           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  9:42             ` Robert Pluim
2023-06-27  9:49               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  9:53                 ` Robert Pluim
2023-06-27 12:06                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27  9:59                 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 12:10                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 14:02                     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-27 11:30               ` 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=83v8f8vkeo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64270@debbugs.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).