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: Wed, 24 Aug 2022 23:57:44 +0200 [thread overview]
Message-ID: <8735dli9t3.fsf@logand.com> (raw)
In-Reply-To: <83sfll4esu.fsf@gnu.org>
On Wed 24 Aug 2022 at 22:33, Eli Zaretskii <eliz@gnu.org> wrote:
>> (defun set-text-height (new-height)
>> (set-face-attribute 'default nil :height new-height))
>>
>> How could I achieve what you suggest so that setting the font height
>> would also apply to menu item X resource font?
>
> Make the function write to the ~/.Xresources file?
>
> Of course, X doesn't necessarily understand the Emacs units of
> measuring fonts, for example the relative units. So eventually you'll
> need separate customizations. However, I don't expect you to have to
> change these customizations too frequently.
The point of C-+ and C-- bindings is that I can just press a key and
grow or shrink the font. That is essential for me. My gui terminal can
do that out of the box, my console can do that with a bit of elisp
calling setfont, firefox can do that out of the box, and gui Emacs can
do that using the code I showed earlier; except the menu text we are
discussing.
This font size change happens on demand, when a key is pressed.
I guess writing to the ~/.Xresources file would work only on startup.
Then there seems to be the issue you said that Emacs and X has different
idea of describing fonts/units.
It is just complex and inconvenient.
> More generally, I don't see a way around the fact that different parts
> of the system need to be customized differently.
Why?
At the moment, it is the consequence of the way the no-toolkit menu is
implemented.
But surely it could be possible to change it to customize no-toolkit
menu text the same way as any other face.
> Many programs have
> their own init files, and some even have more than one: for example,
> Bash, GDB, and any other program that uses Readline will typically
> have customizations in ~/.inputrc, in addition to the program-specific
> init file, such as ~/.gdbinit for GDB.
This is not only about init files.
This is about making it not to have more init files, because unlike
customizing and changing faces, customizing a different system out of
Emacs is complex, fragile, inconvenient and might be impossible (is it
possible to change the menu text X resource on key press?).
next prev parent reply other threads:[~2022-08-24 21:57 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 [this message]
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
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=8735dli9t3.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).