From: Christopher Dimech <dimech@gmx.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
carlmarcos@tutanota.com, 56357@debbugs.gnu.org
Subject: bug#56357: Request for font size adaptation that fits window
Date: Tue, 5 Jul 2022 17:33:28 +0200 [thread overview]
Message-ID: <trinity-d764a07a-9c9a-416a-90f0-1907aef97340-1657035208694@3c-app-mailcom-bs07> (raw)
In-Reply-To: <87tu7v6cg1.fsf@gnus.org>
> Sent: Tuesday, July 05, 2022 at 11:11 PM
> From: "Lars Ingebrigtsen" <larsi@gnus.org>
> To: carlmarcos@tutanota.com
> Cc: "Eli Zaretskii" <eliz@gnu.org>, 56357@debbugs.gnu.org
> Subject: bug#56357: Request for font size adaptation that fits window
>
> carlmarcos@tutanota.com writes:
>
> > Correct, a dynamic resizing based on "longest in the buffer". I would
> > say that one would not want frequent resizing either. Though I am not
> > best to state how the dynamic resizing could get activated. Then
> > again there should be a limit of the size of the font for instances
> > where the resizing would get too big for files with short lines.
>
> Oh, OK. I'm not sure I think that's something many people would find
> useful -- people usually choose a fill-column/frame width/font size
> that's suitable for each other. Making lines in a buffer shorter, for
> instance, to be able to jack up the font size isn't something I think
> would be popular.
It all depends how often the longest line in modified. I can see the problem
with dynamic resizing.
Perhaps it can be an extension of `C-x C-+' and `C-x C--' so users would
not have press them multiple times for code to fit window. And be able to
set some other variables so that the result the user sees is optimal as much
as possible.
next prev parent reply other threads:[~2022-07-05 15:33 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
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 [this message]
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
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=trinity-d764a07a-9c9a-416a-90f0-1907aef97340-1657035208694@3c-app-mailcom-bs07 \
--to=dimech@gmx.com \
--cc=56357@debbugs.gnu.org \
--cc=carlmarcos@tutanota.com \
--cc=eliz@gnu.org \
--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 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).