From: Kenichi Handa <handa@m17n.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: lekktu@gmail.com, 870@emacsbugs.donarmstrong.com, emacs-devel@gnu.org
Subject: bug#870: Repeatable instance of bug#870
Date: Wed, 07 Jan 2009 10:07:02 +0900 [thread overview]
Message-ID: <E1LKMsw-0005wG-G6__45106.2184446075$1231291499$gmane$org@etlken.m17n.org> (raw)
In-Reply-To: <4961E7F7.2000509@gnu.org> (message from Jason Rumney on Mon, 05 Jan 2009 18:59:03 +0800)
In article <4961E7F7.2000509@gnu.org>, Jason Rumney <jasonr@gnu.org> writes:
> Juanma Barranquero wrote:
> > emacs -Q --eval "(desktop-save-mode 1)" ChangeLog.870
> >
> I can also reproduce the bug with C-x RET r utf-8-dos after visiting the
> file normally.
I can reproduce it by that recipe.
> It appears that there is a bug in all the decode_coding_* functions when
> a CR lies on a CHARBUF_SIZE (0x4000) boundary with a matching LF on the
> other side of the boundary.
> They all do something like:
> if (eol_crlf && c1 == '\r')
> ONE_MORE_BYTE (byte_after_cr);
> but ONE_MORE_BYTE will abort the decode if it reaches the end of the
> buffer, leaving the CR in limbo between having been read and being added
> to the buffer. Then on decoding the subsequent block, the initial LF
> does not trip the normal CRLF decoding, so it is put into the buffer.
??? decode_coding_* gets bytes from coding->source and
produces characters in CHARBUF. So, I think the above
analysis is not correct.
As normal visiting of ChangeLog.870 doesn't have the problem
but revisiting it causes the problem, I think the bug is in
Finsert_file_contents; perhaps in the handling of REPLACE.
I'll have a look at it.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-01-07 1:07 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 5:03 Repeatable instance of bug#870 Juanma Barranquero
2009-01-05 5:05 ` Juanma Barranquero
2009-01-05 10:59 ` bug#870: " Jason Rumney
2009-01-05 10:59 ` Jason Rumney
2009-01-05 11:12 ` Juanma Barranquero
2009-01-05 11:12 ` Juanma Barranquero
2009-01-05 11:22 ` Jason Rumney
2009-01-05 11:22 ` Jason Rumney
2009-01-05 11:31 ` Juanma Barranquero
2009-01-05 13:50 ` Jason Rumney
2009-01-05 13:50 ` Jason Rumney
2009-01-05 14:28 ` Juanma Barranquero
2009-01-05 14:28 ` Juanma Barranquero
2009-01-05 11:31 ` Juanma Barranquero
2009-01-07 1:07 ` Kenichi Handa
2009-01-07 6:53 ` Kenichi Handa
2009-01-07 8:19 ` martin rudalics
2009-01-07 12:29 ` Kenichi Handa
2009-01-07 15:33 ` martin rudalics
2009-01-13 2:30 ` Kenichi Handa
2009-01-13 4:06 ` Eli Zaretskii
2009-01-07 9:43 ` Juanma Barranquero
[not found] ` <496489D2.8030902@gnu.org>
2008-09-03 11:03 ` bug#870: Missing ^J in ChangeLog Juanma Barranquero
2008-09-03 12:50 ` martin rudalics
2008-09-03 15:20 ` Juanma Barranquero
2008-10-22 15:14 ` Juanma Barranquero
2008-10-22 19:45 ` Eli Zaretskii
2008-10-22 20:15 ` Lennart Borgman (gmail)
2008-10-22 21:08 ` Eli Zaretskii
2008-10-22 21:22 ` Lennart Borgman (gmail)
2008-10-22 22:06 ` Eli Zaretskii
2008-10-22 22:26 ` Lennart Borgman
2008-10-22 23:10 ` Lennart Borgman
2008-10-22 21:58 ` Juanma Barranquero
2008-10-22 22:17 ` Eli Zaretskii
2008-10-22 23:32 ` Juanma Barranquero
2008-10-22 23:41 ` Juanma Barranquero
2008-10-23 0:39 ` Lennart Borgman
2008-10-23 13:34 ` Juanma Barranquero
2009-01-07 11:00 ` bug#870: marked as done (Missing ^J in ChangeLog) Emacs bug Tracking System
[not found] ` <f7ccd24b0901070301t221f906atf75f8632dcf1c41@mail.gmail.com>
2009-01-07 11:10 ` bug#870: Repeatable instance of bug#870 Jason Rumney
2009-01-07 9:43 ` Juanma Barranquero
2009-01-07 6:53 ` Kenichi Handa
2009-01-07 1:07 ` Kenichi Handa [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-05 5:03 Juanma Barranquero
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='E1LKMsw-0005wG-G6__45106.2184446075$1231291499$gmane$org@etlken.m17n.org' \
--to=handa@m17n.org \
--cc=870@emacsbugs.donarmstrong.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=lekktu@gmail.com \
/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.