From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19300@debbugs.gnu.org
Subject: bug#19300: 24.4.51; visual-line-mode messes up after-string rendering when it spans all window columns
Date: Tue, 09 Dec 2014 19:30:46 +0200 [thread overview]
Message-ID: <548731C6.2000500@yandex.ru> (raw)
In-Reply-To: <83zjawx0om.fsf@gnu.org>
On 12/09/2014 06:11 PM, Eli Zaretskii wrote:
> This means every character is 8 pixels wide, so I'd expect the
> wrapping to occur around 256-pixel wide window.
Or 272 (34 columns), if we're talking the first example. Right?
> These are not the numbers we need, we need what this returns:
>
> M-: (window-width nil t) RET
All right, thanks. So, this time I ended up increasing the window width
by 1 pixel, and wrapping disappeared. The widths in pixels:
288 total, 272 body: text is wrapped.
289 total, 273 body: no wrapping.
>> It's fairly hard to reach 288px though, because dragging with the mouse
>> still moves the window border in jumps (even though not by columns).
>
> Perhaps set window-resize-pixelwise non-nil.
Ok, but that doesn't seems to make much of a difference: I have the
frame maximized when experimenting with this (although that's not
required to reproduce the problem), and there are only two windows.
next prev parent reply other threads:[~2014-12-09 17:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 23:50 bug#19300: 24.4.51; visual-line-mode messes up after-string rendering when it spans all window columns Dmitry Gutov
2014-12-08 3:46 ` Eli Zaretskii
2014-12-08 10:14 ` Dmitry Gutov
2014-12-08 16:04 ` Eli Zaretskii
2014-12-08 16:40 ` Dmitry Gutov
2014-12-08 17:03 ` Eli Zaretskii
2014-12-08 18:47 ` Dmitry Gutov
2014-12-08 20:39 ` Eli Zaretskii
2014-12-09 0:51 ` Dmitry Gutov
2014-12-09 16:11 ` Eli Zaretskii
2014-12-09 17:30 ` Dmitry Gutov [this message]
2014-12-09 17:51 ` Eli Zaretskii
2014-12-09 18:38 ` Dmitry Gutov
2014-12-09 18:50 ` Eli Zaretskii
2014-12-10 17:58 ` Eli Zaretskii
2014-12-10 22:50 ` Dmitry Gutov
2014-12-11 3:42 ` Eli Zaretskii
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=548731C6.2000500@yandex.ru \
--to=dgutov@yandex.ru \
--cc=19300@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).