From: Vitalie Spinu <spinuvit@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20022@debbugs.gnu.org
Subject: bug#20022: 24.4.90; window-body-height, window-body-width wrong value after text-scale-adjust
Date: Sat, 07 Mar 2015 22:46:52 +0200 [thread overview]
Message-ID: <87oao41qo3.fsf@gmail.com> (raw)
In-Reply-To: <83pp8kllrh.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 07 Mar 2015 20:12:34 +0200")
>>> Eli Zaretskii on Sat, 07 Mar 2015 20:12:34 +0200 wrote:
> having a term that needs to be explained by telling how to compute it
> sends a confusing message.
It gives an operational definition of "lines", which is a valid
definition. It's confusing to see 100 lines in a buffer and to be told
that there are 25 "lines".
>> I simply need the number of characters that can be fit in a single line
>> in order to set the sub-process output width.
> This can only be meaningfully computed if the text emitted by the
> subprocess will be rendered in its entirety using the default face.
Sure, but that's the case of window-height as well. It's based on the
size of a particular font regardless of what's contained in the buffer.
> Not that I know of. We could provide a function for that, if this
> functionality is deemed important enough.
I guess the core of the problem is that having a width/height computed
using default buffer font is more useful than using frame default
font. Given that the docs were never clear maybe the behavior of
existing functions could be changed. Or an additional font-toggling
argument added to those.
Vitalie
next prev parent reply other threads:[~2015-03-07 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 22:31 bug#20022: 24.4.90; window-body-height, window-body-width wrong value after text-scale-adjust Vitalie Spinu
2015-03-07 9:41 ` martin rudalics
2015-03-07 9:49 ` Eli Zaretskii
2015-03-07 16:09 ` Vitalie Spinu
2015-03-07 17:58 ` martin rudalics
2015-03-07 20:49 ` Vitalie Spinu
2015-03-07 18:12 ` Eli Zaretskii
2015-03-07 20:46 ` Vitalie Spinu [this message]
2015-03-08 3:47 ` Eli Zaretskii
2015-03-08 10:03 ` martin rudalics
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=87oao41qo3.fsf@gmail.com \
--to=spinuvit@gmail.com \
--cc=20022@debbugs.gnu.org \
--cc=eliz@gnu.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).