From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 953033@bugs.debian.org, yamaoka@jpl.org, jidanni@jidanni.org,
39901@debbugs.gnu.org
Subject: bug#39901: Emacs needs to update window-width when the user updates the text size
Date: Wed, 05 Aug 2020 16:51:31 +0200 [thread overview]
Message-ID: <87sgd1jgcs.fsf@gnus.org> (raw)
In-Reply-To: <835z9x9mxp.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 Aug 2020 17:39:30 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I do: there's no bug here -- window-width is documented to return a
> value in terms of the frame's canonical character width (i.e. it uses
> the dimensions of the frame's default font). And that doesn't change
> when you change the font only for a single buffer.
>
> However, window-width can be asked to return the value in pixels, if
> someone wants that, and then one can compute the width in units of any
> other, larger or smaller, font.
>
> IOW, if some applications produce unexpected or unpleasant effects
> when the buffer text is resized, those applications need to be
> sensitive to such resizing. But changing the semantics of a veteran
> API like suggested here is a non-starter, as it would definitely break
> gobs of existing code.
Yeah, that's true. I had completely forgotten that C-x C-+ only affects
the current buffer, so resizing the window on that command would be
nonsensical.
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2020-08-05 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878skhphb5.8.fsf@jidanni.org>
[not found] ` <b4msgip14kb.fsf@jpl.org>
2020-03-04 14:19 ` bug#39901: Emacs needs to update window-width when the user updates the text size 積丹尼 Dan Jacobson
2020-03-04 14:38 ` Drew Adams
2020-03-04 23:00 ` Katsumi Yamaoka
2020-03-05 0:28 ` 積丹尼 Dan Jacobson
2020-08-05 12:04 ` Lars Ingebrigtsen
2020-08-05 14:39 ` Eli Zaretskii
2020-08-05 14:51 ` Lars Ingebrigtsen [this message]
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=87sgd1jgcs.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=39901@debbugs.gnu.org \
--cc=953033@bugs.debian.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.org \
--cc=yamaoka@jpl.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.