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: Mon, 08 Dec 2014 20:47:02 +0200 [thread overview]
Message-ID: <5485F226.2040104@yandex.ru> (raw)
In-Reply-To: <83lhmixedt.fsf@gnu.org>
On 12/08/2014 07:03 PM, Eli Zaretskii wrote:
>> The scenarios intentionally resize the newly popped window to make sure
>> it's the right size.
>
> I know. But facts are stubborn things: I still need to resize.
Please don't, it invalidates the point of this bug report.
>> But I can open a different window, enable visual-line-mode, take its
>> (window-width), insert that numbers of characters on one line and not
>> see them wrapped.
>
> Then please show a recipe for that.
Do I need to? The fact that you don't see the problem when executing my
scenario means that the above must always work well for you.
>> Could this be a bug in `enlarge-window-horizontally' and/or `window-width'?
>
> Maybe, there's no way of guessing in advance. It could also be that
> this particular font has some weird metrics in it.
Could you suggest how to proceed debugging it? If you can't reproduce
the problem with my scenario, can I send you some data from my session?
I reproduce it with 100% probability, in GUI mode, without any
customization (emacs -Q).
>>> If so, I cannot
>>> reproduce this: I see both the overlay and the buffer text wrap
>>> exactly identically.
Right, same here, albeit (in the first case) when (window-width) returns
34, and (window-pixel-width) returns 288.
I can also drag the left window border a bit, so that (window-width)
still returns 34, but (window-pixel-width) is 291, then the lines in the
test buffer become not wrapped.
next prev parent reply other threads:[~2014-12-08 18:47 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 [this message]
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
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=5485F226.2040104@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).