all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Johan Bockgård" <bojohan@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9771@debbugs.gnu.org
Subject: bug#9771: 24.0.90; Redisplay problems with control characters
Date: Wed, 19 Oct 2011 03:06:09 +0200	[thread overview]
Message-ID: <87ipnlzt6m.fsf@gnu.org> (raw)
In-Reply-To: <E1RG9De-0004Zm-5N@fencepost.gnu.org> (Eli Zaretskii's message of "Tue, 18 Oct 2011 08:56:34 -0400")

Eli Zaretskii <eliz@gnu.org> writes:

> Consuming the last glyph of a display vector means that the next call
> to set_iterator_to_next will detect that the display vector is
> exhausted, and will advance to the next buffer position, the one after
> the position which we just passed by consuming all the glyphs from the
> display vector used to display the character at that position. Thus,
> "buffer position reached".

It seems that BUFFER_POS_REACHED_P at least misses the opportunity to
stop immediately before *any* glyph in the display vector has been
consumed, i.e. when dpvec_index == 0. (Or the problem is not with
BUFFER_POS_REACHED_P but with how it's being used.)

[...]
> In practice, after correcting the bug that caused the assertion
> violation, I can no longer reproduce the situation where we stop in
> the middle of the ^@ character.  If you can show me a recipe for
> winding up in the middle of a display vector under these or similar
> circumstances, I will have another look.

emacs -Q

C-u 2000 C-q 0 RET

Notice that the lines visible in the window start with "@^".

Press <up> until the top of the buffer just scrolls into view.

Notice that lines before point start with "^@", and lines after
point start with "@^".

Change BUFFER_POS_REACHED_P (or something) so that dpvec_index == 0 is
an acceptable stop position and this problem doesn't happen.





  parent reply	other threads:[~2011-10-19  1:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-16 22:24 bug#9771: 24.0.90; Redisplay problems with control characters Johan Bockgård
2011-10-17  7:48 ` Eli Zaretskii
2011-10-17 14:18   ` Eli Zaretskii
2011-10-17 21:04   ` Johan Bockgård
2011-10-18 12:56     ` Eli Zaretskii
2011-10-18 16:58       ` Eli Zaretskii
2011-10-20 12:43         ` Eli Zaretskii
2011-10-19  1:06       ` Johan Bockgård [this message]
2011-10-19 11:49         ` Eli Zaretskii
2011-10-17 17:06 ` Eli Zaretskii
2011-10-17 19:16 ` 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=87ipnlzt6m.fsf@gnu.org \
    --to=bojohan@gnu.org \
    --cc=9771@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 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.