From: Drew Adams <drew.adams@oracle.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: "cpitclaudel@gmail.com" <cpitclaudel@gmail.com>,
"48307@debbugs.gnu.org" <48307@debbugs.gnu.org>
Subject: bug#48307: [External] : bug#48307: Feature request: provide default keybindings to change the font size in all windows
Date: Mon, 10 May 2021 15:26:22 +0000 [thread overview]
Message-ID: <SA2PR10MB4474FC6ADA103F34BB1187EAF3549@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <e27b2f896d1ec13b2987@heytings.org>
> >>> Why does it make sense to inhibit frame resizing in this case? I
> >>> think it will make an ugly display: mode-line text will spill over,
> >>> lines will become wrapped, etc.
> >>
> >> Because (1) it's what other programs do,
> >
> > See what I wrote. That can be good and bad. Why limit Emacs to what
> > other programs do?
>
> I don't want to limit Emacs to anything... but not everything can be
> bound to a key or a mouse event. Perhaps this could become a defcustom,
> defaulting to t?
,----
| text-scale-resize-window is a variable defined in `face-remap+.el'.
|
| Its value is t
|
| Documentation:
| Non-nil means text scaling resizes the window or frame accordingly.
| For example, if you use `C-x C--' (`text-scale-decrease')' to make the
| text smaller, then the window or frame is made smaller by a similar
| factor.
|
| If the window is not alone in its frame, then the window is resized.
| Otherwise, the frame is resized (provided you also use library
| `fit-frame.el'). The frame is always resized both horizontally and
| vertically.
|
| You can customize this variable.
`----
next prev parent reply other threads:[~2021-05-10 15:26 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SA2PR10MB4474FC6ADA103F34BB1187EAF3549@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=48307@debbugs.gnu.org \
--cc=cpitclaudel@gmail.com \
--cc=gregory@heytings.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.