unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Hlavaty <tom@logand.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 57372@debbugs.gnu.org
Subject: bug#57372: no-toolkit menu popups do not respect emacs font configuration
Date: Fri, 26 Aug 2022 09:13:55 +0200	[thread overview]
Message-ID: <877d2vbhos.fsf@logand.com> (raw)
In-Reply-To: <83ilmg2llb.fsf@gnu.org>

On Thu 25 Aug 2022 at 22:02, Eli Zaretskii <eliz@gnu.org> wrote:
>> Frequency is not that relevant.  Convenience is relevant.  It should
>> happen after key press.
>
> This is an exaggeration, and as such, not useful.  It is unreasonable
> to expect everything be done at a keypress.  Infrequent operations can
> be less convenient than frequent ones, because that inconvenience
> basically happens once in a blue moon.

It happens as frequently or as rarely as the user chooses to press the
relevant key.  In other words, it is under control of the user, not
somebody else.

>> It is not something I invented, it is important use-case and pretty
>> much essential part of GUI programs these days.  Try for example C-+
>> and C-- in firefox or xfce4-terminal.
>
> When I do that in Firefox, the displayed text is resized, but not the
> menus or the tool bar.

True.

I gave the example because it seed to me you did not understand why
would somebody want to press C-+ or C-- to resize font instead of
changing a configuration and restarting.

Now I see that you mean specifically the Firefox menu.
Well, the Firefox menu uses a widget toolkit.

no-toolkit Emacs is not supposed to use a widget toolkit as far as I
understand it.  I was hoping that there would not be an alien library
with all the negatives of alien widget toolkit, or in this case even
worse (XMenu does not respect my desktop font settings, font
configuration is inconvenient, it looks bad and is unreadable by
default).

>> > I guess I don't understand why one would need to change the size
>> > frequently, especially the size of the menu items, which basically
>> > stay unchanged.
>> 
>> We already discussed several issues with the X resources based text:
>> 
>> - The font configuration is alien to emacs with many issues and downsides.
>> - It is not possible to change it dynamically.
>
> That's nowhere near a catastrophe for such an infrequent setting.

Dismissing the use-case is one way to solve this.

What I would like to have is kind of similar behaviour as tty emacs on
xfce4-terminal except with additional benefits of graphics capabilities
built into the GUI Emacs.  I like the way Emacs buffers work and that
they have dynamically customizable faces.  I do not like alien widget
toolkits getting in the way.





  reply	other threads:[~2022-08-26  7:13 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 20:47 bug#57372: no-toolkit menu popups do not respect emacs font configuration Tomas Hlavaty
2022-08-24  2:29 ` Eli Zaretskii
2022-08-24  8:15   ` Tomas Hlavaty
2022-08-24 10:56     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 11:23       ` Eli Zaretskii
2022-08-24 12:11         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 12:27           ` Eli Zaretskii
2022-08-24 12:34             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 12:43               ` Eli Zaretskii
2022-08-24 13:01                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 13:21                   ` Eli Zaretskii
2022-08-24 13:23                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 13:25                       ` Eli Zaretskii
2022-08-24 13:39                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 14:23                           ` Eli Zaretskii
2022-08-24 19:07                             ` Tomas Hlavaty
2022-08-24 19:36                               ` Eli Zaretskii
2022-08-24 23:10                                 ` Stefan Kangas
2022-08-25  1:08                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 17:49             ` Tomas Hlavaty
2022-08-24 17:59               ` Eli Zaretskii
2022-08-24 19:01                 ` Tomas Hlavaty
2022-08-24 19:33                   ` Eli Zaretskii
2022-08-24 21:57                     ` Tomas Hlavaty
2022-08-25  1:40                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25  6:42                       ` Eli Zaretskii
2022-08-25 18:21                         ` Tomas Hlavaty
2022-08-25 19:02                           ` Eli Zaretskii
2022-08-26  7:13                             ` Tomas Hlavaty [this message]
2022-08-26  7:42                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 20:06                             ` Tomas Hlavaty
2022-09-14  1:59                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26  1:13                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25  1:28                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25  1:26                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25  1:25               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-24 16:15         ` Tomas Hlavaty
2022-08-24 16:32           ` Eli Zaretskii
2022-08-24 18:54             ` Tomas Hlavaty
2022-08-24 19:28               ` Eli Zaretskii
2022-08-24 22:59                 ` Tomas Hlavaty
2022-08-25  6:51                   ` Eli Zaretskii
2022-08-25 19:07                     ` Tomas Hlavaty
2022-08-25 19:15                       ` Eli Zaretskii
2022-08-26  7:19                         ` Tomas Hlavaty
2022-08-26 10:35                           ` Eli Zaretskii
2022-08-26 10:54                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 11:00                               ` Eli Zaretskii
2022-08-26 11:18                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 11:31                                   ` Eli Zaretskii
2022-08-24 11:47       ` Lars Ingebrigtsen
2022-08-24 16:09       ` Tomas Hlavaty
2022-08-25  1:09         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25 19:18           ` Tomas Hlavaty
2022-08-26  1:11             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26  6:54               ` Tomas Hlavaty

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=877d2vbhos.fsf@logand.com \
    --to=tom@logand.com \
    --cc=57372@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.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).