all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Constantine Vetoshev <vetoshev@gmail.com>
Cc: 16470-done@debbugs.gnu.org
Subject: bug#16470: 24.3.50; term mode and newlines with some window configurations
Date: Thu, 23 Jan 2014 09:53:05 +0100	[thread overview]
Message-ID: <52E0D871.8080905@gmx.at> (raw)
In-Reply-To: <1E7C0748-177E-4286-8819-05238421911E@gmail.com>

 > I made a build with your latest changes, and it seems to work. window-width and window-text-width now return the same values in all window configurations I tried, and term.el works as expected.

OK.  Closing this bug.

 > That said, I now don't see any difference between window-body-width, window-text-width, and window-width when the PIXELWISE argument is omitted or nil.

Correct.  IIRC this was the case with Emacs 23 as well.

The rationale is the following: Intuitively, the total width of a window
(including scrollbars, fringes, ....) should be larger than its body
width.  Now consider two side by side windows whose pixel widths equal
72 and 66 so their parent window has 138 pixels.  With a character width
of 8, the parent has 17 total columns and the larger child 9 columns.

I have to give the other window 8 columns since otherwise the sum of the
width of these windows would not match the width of their parent with
unpredictable consequences for functions like `window-edges' whose
return values are often used to check whether two windows are adjacent
to each other.

Now if the smaller of these windows has no scrollbars, fringes, margins,
dividers ... using the previous calculation would give it a body width
of 9 columns (rounding up the result of 66 / 8) exceeding its nominal
total width.

Thanks, martin





  reply	other threads:[~2014-01-23  8:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 23:15 bug#16470: 24.3.50; term mode and newlines with some window configurations Constantine Vetoshev
2014-01-17  4:29 ` Constantine Vetoshev
2014-01-17  7:51 ` martin rudalics
2014-01-17 16:52   ` Constantine Vetoshev
2014-01-17 19:06     ` martin rudalics
2014-01-17 19:26       ` Constantine Vetoshev
2014-01-18 12:07         ` martin rudalics
2014-01-18 16:03           ` Constantine Vetoshev
2014-01-18 17:24             ` martin rudalics
2014-01-18 18:43               ` Constantine Vetoshev
2014-01-19  9:31               ` martin rudalics
2014-01-19 16:11                 ` Constantine Vetoshev
2014-01-19 17:30                   ` martin rudalics
2014-01-22 10:35                     ` martin rudalics
2014-01-22 16:00                       ` Constantine Vetoshev
2014-01-23  8:53                         ` martin rudalics [this message]
2014-01-18 11:36     ` Jan Djärv

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=52E0D871.8080905@gmx.at \
    --to=rudalics@gmx.at \
    --cc=16470-done@debbugs.gnu.org \
    --cc=vetoshev@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.