all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Vitalie Spinu <spinuvit@gmail.com>, 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: Sun, 08 Mar 2015 11:03:26 +0100	[thread overview]
Message-ID: <54FC1E6E.4080205@gmx.at> (raw)
In-Reply-To: <87oao41qo3.fsf@gmail.com>

 > 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.

You mean that switching to another buffer in a window could change the
nominal height of that window?

I have no opinion on this because I don't care about line-/column values
returned by these functions.  The only thing I do care about is that if
you have two side-by-side windows, the value of `window-left-column' of
the right window equals the sum of `window-left-column' and
`window-total-width' of the window on the left.  Otherwise, windmove's
functions might fail and I have no intention to fix them again.

martin





      parent reply	other threads:[~2015-03-08 10:03 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
2015-03-08  3:47         ` Eli Zaretskii
2015-03-08 10:03         ` martin rudalics [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=54FC1E6E.4080205@gmx.at \
    --to=rudalics@gmx.at \
    --cc=20022@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=spinuvit@gmail.com \
    /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.