From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: 48307@debbugs.gnu.org
Subject: bug#48307: Feature request: provide default keybindings to change the font size in all windows
Date: Sun, 09 May 2021 11:23:10 +0300 [thread overview]
Message-ID: <83h7jc8gep.fsf@gnu.org> (raw)
In-Reply-To: <603bbc01-b1a2-b367-f54e-59a57475cbfe@gmail.com> (message from Clément Pit-Claudel on Sun, 9 May 2021 03:09:45 -0400)
> From: Clément Pit-Claudel <cpitclaudel@gmail.com>
> Date: Sun, 9 May 2021 03:09:45 -0400
>
> Emacs has keybindings to change the font size in the current buffer (C-x C-=, etc which use text-scale-adjust). We don't have keybindings for commands to change the font size globally, and in fact we don't have commands for that purpose at all, AFAICT.
>
> My students keep running into this issue, and it seems pretty common online, too:
It is not clear what should the requested feature do, and the links
you provided each talk about different aspects of the problem without
actually completely defining the requested functionality.
So: what should be the effect of this "global" change of the "font
size"? Some thought-provoking questions:
. should this affect only the faces whose fonts don't define their
own size, or should it affect _all_ fonts?
. should this really affect _all_ the buffers? e.g., what about the
minibuffer and the echo-area buffers?
. should this affect all the frames or just the currently selected
frame? what about future frames?
. should this affect the mode line?
. should this affect tooltips?
. should this affect the fringes and their bitmaps?
. should this affect the menu bar, the drop-down menus, and the GUI
dialogs?
We need a clear understanding of the feature before we implement it,
IMO.
Thanks.
next prev parent reply other threads:[~2021-05-09 8:23 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 7:09 bug#48307: Feature request: provide default keybindings to change the font size in all windows Clément Pit-Claudel
2021-05-09 8:23 ` Eli Zaretskii [this message]
2021-05-09 15:31 ` Clément Pit-Claudel
2021-05-09 16:08 ` Eli Zaretskii
2021-05-09 16:39 ` bug#48307: [External] : " Drew Adams
2021-05-09 16:58 ` Eli Zaretskii
2021-05-09 22:30 ` Clément Pit-Claudel
2021-05-09 16:30 ` Drew Adams
2021-05-09 8:43 ` martin rudalics
2021-05-09 15:18 ` Clément Pit-Claudel
2021-05-09 16:05 ` bug#48307: [External] : " Drew Adams
2021-05-10 8:24 ` martin rudalics
2021-05-10 14:17 ` bug#48307: [External] : " Drew Adams
2021-05-10 14:17 ` Gregory Heytings
2021-05-10 14:26 ` Eli Zaretskii
2021-05-10 14:34 ` Gregory Heytings
2021-05-10 14:42 ` bug#48307: [External] : " Drew Adams
2021-05-10 15:07 ` Gregory Heytings
2021-05-10 15:26 ` Drew Adams
2021-05-10 14:53 ` Clément Pit-Claudel
2021-05-10 15:22 ` bug#48307: [External] : " Drew Adams
2021-05-10 15:36 ` Clément Pit-Claudel
2021-05-10 16:16 ` Eli Zaretskii
2021-05-10 16:26 ` Clément Pit-Claudel
2021-05-10 16:45 ` Clément Pit-Claudel
2021-05-10 18:16 ` Gregory Heytings
2021-05-10 18:34 ` Clément Pit-Claudel
2021-05-10 18:46 ` Eli Zaretskii
2021-05-10 19:04 ` Clément Pit-Claudel
2021-05-10 19:35 ` Gregory Heytings
2021-05-10 19:41 ` Clément Pit-Claudel
2021-05-10 19:47 ` Gregory Heytings
2021-05-25 7:58 ` Gregory Heytings
2021-05-25 12:31 ` Eli Zaretskii
2021-05-25 12:58 ` Gregory Heytings
2021-05-25 13:12 ` Eli Zaretskii
2021-05-25 13:16 ` Gregory Heytings
2021-05-25 13:42 ` Eli Zaretskii
2021-05-25 19:43 ` Lars Ingebrigtsen
2022-07-02 13:41 ` Lars Ingebrigtsen
2021-05-09 15:58 ` bug#48307: [External] : " Drew Adams
2021-05-09 21:38 ` Clément Pit-Claudel
2021-05-09 20:16 ` Gregory Heytings
2021-05-09 21:36 ` Clément Pit-Claudel
2021-05-09 22:03 ` Gregory Heytings
2021-05-09 22:15 ` Clément Pit-Claudel
2021-05-09 22:56 ` Gregory Heytings
2021-05-10 14:19 ` Eli Zaretskii
2021-05-10 14:24 ` Gregory Heytings
2021-05-10 14:33 ` Eli Zaretskii
2021-05-10 16:24 ` Gregory Heytings
2021-05-10 14:33 ` bug#48307: [External] : " Drew Adams
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=83h7jc8gep.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48307@debbugs.gnu.org \
--cc=cpitclaudel@gmail.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).