From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: holtzermann17@gmail.com, 19194@debbugs.gnu.org
Subject: bug#19194: 24.4.50; `window-body-width' is not dynamic relative to font size changes
Date: Sat, 20 Dec 2014 20:29:29 +0200 [thread overview]
Message-ID: <83ppbeqinq.fsf@gnu.org> (raw)
In-Reply-To: <5495B73C.6060006@gmx.at>
> Date: Sat, 20 Dec 2014 18:51:56 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: holtzermann17@gmail.com, 19194@debbugs.gnu.org
>
> >> Probably to know how many characters fit into a line. With a
> >> proportional font.
> >
> > But for a proportional font, that question has no meaningful answer.
> > Using the maximum width could yield a result that it a gross
> > underestimation. I fail to see how this could be more useful than
> > using the average width.
>
> Are we sure that all numbers fit into the average width. If not, we can
> get problems with line numbers.
Like I said: you will get a wrong answer either way. I think this is
simply the wrong way to do it. I cannot suggest a better way without
knowing more about the particular application.
> BTW you probably might want to close bugs 1255, 8379 and 10960 now ;-)
So can you ;-)
> >> He wants the width of a default font "M" (where the default fount could
> >> be proportional) filtered by the frame it appears on and the remapping
> >> specified for the buffer the character appears in.
> >
> > Once you get the font used by a face on that frame and buffer, the
> > font parameters are fixed.
>
> I lost you here. Does that mean that with proportional fonts an "M" and
> an "I" have different fonts?
I'm saying that specifying the font by a face on a frame makes any
"filtering" redundant.
next prev parent reply other threads:[~2014-12-20 18:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 13:47 bug#19194: 24.4.50; `window-body-width' is not dynamic relative to font size changes Joe Corneli
2014-11-26 15:55 ` Stefan Monnier
2014-11-26 16:34 ` Joe Corneli
2014-11-26 17:06 ` Eli Zaretskii
2014-11-26 16:04 ` Eli Zaretskii
2014-11-27 9:44 ` martin rudalics
2014-11-27 10:54 ` Joe Corneli
2014-11-27 18:35 ` martin rudalics
2014-11-27 18:52 ` Eli Zaretskii
2014-11-27 19:58 ` martin rudalics
2014-11-27 20:43 ` Eli Zaretskii
2014-11-28 7:29 ` martin rudalics
2014-11-28 8:49 ` Eli Zaretskii
2014-11-28 18:38 ` martin rudalics
2014-11-28 19:20 ` Eli Zaretskii
2014-12-19 19:40 ` Eli Zaretskii
2014-12-20 10:10 ` martin rudalics
2014-12-20 11:52 ` Joe Corneli
2014-12-20 14:49 ` martin rudalics
2014-12-20 16:18 ` Eli Zaretskii
2014-12-20 16:31 ` martin rudalics
2014-12-20 16:47 ` Eli Zaretskii
2014-12-20 17:51 ` martin rudalics
2014-12-20 18:29 ` Eli Zaretskii [this message]
2014-11-27 20:23 ` Joe Corneli
2014-11-28 7:27 ` martin rudalics
2014-11-27 16:17 ` Eli Zaretskii
2014-11-27 18:35 ` martin rudalics
2014-11-27 18:46 ` Eli Zaretskii
2014-11-27 19:58 ` martin rudalics
2014-11-27 20:37 ` Eli Zaretskii
2014-11-28 7:27 ` martin rudalics
2014-11-28 8:42 ` Eli Zaretskii
2022-02-10 8:16 ` bug#19194: bug#20022: 24.4.90; window-body-height, window-body-width wrong value after text-scale-adjust Lars Ingebrigtsen
2022-02-10 17:39 ` bug#19194: [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=83ppbeqinq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19194@debbugs.gnu.org \
--cc=holtzermann17@gmail.com \
--cc=rudalics@gmx.at \
/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).