unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: Eli Zaretskii <eliz@gnu.org>, 64270@debbugs.gnu.org
Subject: bug#64270: 30.0.50; Font update for no toolkit menu
Date: Wed, 28 Jun 2023 17:20:55 +0800	[thread overview]
Message-ID: <874jms6iyw.fsf@yahoo.com> (raw)
In-Reply-To: <878rc4t48h.fsf@ledu-giraud.fr> (Manuel Giraud's message of "Wed,  28 Jun 2023 09:50:38 +0200")

Manuel Giraud <manuel@ledu-giraud.fr> writes:

> That is interesting.  This means that a face used in a frame might not
> exists in a form that is loadable by XLoadQueryFont, right?  So I think
> it is real shortcoming of what I wanted to do.

Yes.  The X core font requests can only utilize fonts that are present
on the X server, which precludes using any font from a FreeType-based
font driver.

> Yes, I know.  Everytime I'm trying to do something on oldXMenu this idea
> keep resurfacing.  But it is quite a task and oldXMenu is already here
> and not that bad.  Do you think that child frames could be a starting
> point for menus?

I don't think so; frames are quite resource intensive and slow to
create.  Child frames have also always been a mess, and they are
obscured by ancestor windows.  If we were to implement menus in terms of
frames, it would be better to apply an owner-events grab to an
override-redirect frame (as usual among X clients), but even that would
be slow.





  reply	other threads:[~2023-06-28  9:20 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
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 [this message]
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=874jms6iyw.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=64270@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --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).