From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11199@debbugs.gnu.org
Subject: bug#11199: 24.0.95; killing right-to-left text at eob leads to inconsistent state
Date: Mon, 09 Apr 2012 18:48:16 +0900 [thread overview]
Message-ID: <wlehrxgrrz.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <83d37h8e4u.fsf@gnu.org>
>>>>> On Mon, 09 Apr 2012 12:10:09 +0300, Eli Zaretskii <eliz@gnu.org> said:
> I cannot figure out where these two numbers, 309 and 313, come from.
> If I repeat the recipe and look at the glyph matrix _before_ C-k,
> there are no such buffer positions anywhere in sight there.
I guess this just comes from some white space difference introduced by
copy-and-paste.
> Also, please verify that you see the same buffer positions in the
> glyph matrix as I do. Here's a GDB session I used to this end:
I get the same results on Mac OS X 10.7.3, X11 build.
> (gdb) pmtxrows w->current_matrix
> 0: edges=(1,78),r2l=0,cont=0,trunc=(0,0),at_zv=0
> 1: edges=(78,141),r2l=0,cont=0,trunc=(0,0),at_zv=0
> 2: edges=(141,191),r2l=0,cont=0,trunc=(0,0),at_zv=0
> 3: edges=(191,192),r2l=0,cont=0,trunc=(0,0),at_zv=0
> 4: edges=(192,199),r2l=0,cont=0,trunc=(0,0),at_zv=0
> 5: edges=(199,237),r2l=0,cont=0,trunc=(0,0),at_zv=0
> 6: edges=(237,305),r2l=0,cont=0,trunc=(0,0),at_zv=0
> 7: edges=(305,309),r2l=0,cont=0,trunc=(0,0),at_zv=1
(snip)
What is shown by
(gdb) p w->current_matrix->rows[6].end.pos
at this stage? I get
$7 = {
charpos = 308,
bytepos = 311
}
and it looks "out of sync" because edges=(237,305) for the 6th row.
I hope this is also reproducible at your side.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2012-04-09 9:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-08 2:26 bug#11199: 24.0.95; killing right-to-left text at eob leads to inconsistent state YAMAMOTO Mitsuharu
2012-04-08 7:33 ` Eli Zaretskii
2012-04-08 18:28 ` Michael Welsh Duggan
2012-04-08 18:33 ` Michael Welsh Duggan
2012-04-08 20:03 ` Eli Zaretskii
2012-04-08 20:13 ` Eli Zaretskii
2012-04-08 20:19 ` Michael Welsh Duggan
2012-04-08 20:16 ` Michael Welsh Duggan
2012-04-08 20:20 ` Eli Zaretskii
2012-04-08 20:25 ` Michael Welsh Duggan
2012-04-08 20:37 ` Eli Zaretskii
2012-04-08 20:48 ` Eli Zaretskii
2012-04-08 21:01 ` Michael Welsh Duggan
2012-04-08 21:10 ` Eli Zaretskii
2012-04-08 21:17 ` Michael Welsh Duggan
2012-04-09 6:24 ` Eli Zaretskii
2012-04-08 20:49 ` Michael Welsh Duggan
2012-04-08 21:07 ` Eli Zaretskii
2012-04-09 8:21 ` YAMAMOTO Mitsuharu
2012-04-09 9:32 ` Eli Zaretskii
2012-04-09 9:10 ` Eli Zaretskii
2012-04-09 9:48 ` YAMAMOTO Mitsuharu [this message]
2012-04-09 10:17 ` Eli Zaretskii
2012-04-09 11:07 ` Eli Zaretskii
2012-04-09 11:52 ` Eli Zaretskii
2012-04-09 12:18 ` Michael Welsh Duggan
2012-04-09 12:34 ` Eli Zaretskii
2012-04-09 23:50 ` YAMAMOTO Mitsuharu
2012-04-10 6:27 ` 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=wlehrxgrrz.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=11199@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).