From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
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 22:39:47 +0200 [thread overview]
Message-ID: <837fy1yiy4.fsf@gnu.org> (raw)
In-Reply-To: <5485F226.2040104@yandex.ru>
> Date: Mon, 08 Dec 2014 20:47:02 +0200
> From: Dmitry Gutov <dgutov@yandex.ru>
> CC: 19300@debbugs.gnu.org
>
> >> 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.
I meant a recipe to show one window with the problem and another
without, in the same session. If you achieve that with the same
resizing of a window, it'd be interesting to see.
> 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?
The pixel size of the canonical character of that font, as you get in
your session, would be a good start. E.g., put a breakpoint in
set_cursor_from_row, then step a few lines, and type "pgrow".
Here's the full recipe:
gdb ./emacs
break Fredraw_display
r -Q
Now arrange for the problematic display, and then
M-x redraw-display RET
(gdb) break set_cursor_from_row
(gdb) continue
(gdb) continue
(gdb) next
(gdb) next
(gdb) next
(gdb) pgrow
The first "continue" is because the first time set_cursor_from_row is
entered Emacs is displaying the echo area, whereas I need to see the
window of a normal buffer.
> >>> 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.
The fact that pixel size changes, but the size in characters doesn't
is expected, of course.
next prev parent reply other threads:[~2014-12-08 20:39 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837fy1yiy4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19300@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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.