From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: carlmarcos@tutanota.com, 56357@debbugs.gnu.org
Subject: bug#56357: Request for font size adaptation that fits window
Date: Mon, 04 Jul 2022 17:05:17 +0300 [thread overview]
Message-ID: <83sfnh7z36.fsf@gnu.org> (raw)
In-Reply-To: <87let96l0b.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 04 Jul 2022 15:54:44 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: carlmarcos@tutanota.com, 56357@debbugs.gnu.org
> Date: Mon, 04 Jul 2022 15:54:44 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > With your proposal, how would you determine the target value? If it's
> > just an arbitrary value (80 sounds like an arbitrary one to me), then
> > the recently-added global-text-scale-adjust-resizes-frames variable
> > does the same, just from the other end: the user enlarges the font and
> > the frame follows suit. And since our default frame width is already
> > set for 80 characters, it sounds like we already have the feature you
> > envisioned, no?
>
> I think the user wants to be able to drag a frame to be bigger and get
> the font to be resized to have the same number of columns, so it's not
> the same feature at all.
I'm asking why it matters how you "drag the frame": whether by
actually dragging its edge or by C-M-wheel-up. The results is the
same, no?
And that actually gives an idea: make dragging the frame call the same
function that C-M-wheel-up does.
next prev parent reply other threads:[~2022-07-04 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 12:17 bug#56357: Request for font size adaptation that fits window carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-03 3:39 ` Richard Stallman
2022-07-04 11:01 ` Lars Ingebrigtsen
2022-07-04 11:42 ` Eli Zaretskii
2022-07-04 13:54 ` Lars Ingebrigtsen
2022-07-04 14:05 ` Eli Zaretskii [this message]
2022-07-04 19:25 ` carlmarcos--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-05 11:11 ` Lars Ingebrigtsen
2022-07-05 15:33 ` Christopher Dimech
2022-07-04 15:54 ` 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=83sfnh7z36.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56357@debbugs.gnu.org \
--cc=carlmarcos@tutanota.com \
--cc=larsi@gnus.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.