From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 16433@debbugs.gnu.org
Subject: bug#16433: 24.3.50; find_newline screws up in Rmail buffers
Date: Mon, 13 Jan 2014 22:31:06 +0200 [thread overview]
Message-ID: <83r48b62ut.fsf@gnu.org> (raw)
In-Reply-To: <E1W2nJv-0001gS-S3@fencepost.gnu.org>
> Date: Mon, 13 Jan 2014 14:37:11 -0500
> From: Richard Stallman <rms@gnu.org>
>
>
> mail-fetch-field gave the wrong result for the X-RMAIL-ATTRIBUTES
> field, perhaps because it happened to be last. It included the
> newline after that field in the return value, which is wrong.
> Setting cache-long-scans to nil in the Rmail buffer made the
> bug go away, so I think the problem is in the newline cache.
I agree.
> I think it would be better to fix the underlying bug, rather than turn
> off the cache in Rmail mode.
Again, I agree.
> I suspect that the cache does not handle Rmail's changes in
> narrowing.
No, I don't think so. I suspect it has something to do with
buffer-swap-text.
Is it possible to have a reproducible recipe for this problem?
next prev parent reply other threads:[~2014-01-13 20:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 19:37 bug#16433: 24.3.50; find_newline screws up in Rmail buffers Richard Stallman
2014-01-13 20:31 ` Eli Zaretskii [this message]
2014-01-14 17:06 ` Richard Stallman
2014-01-14 17:36 ` Eli Zaretskii
2014-01-15 12:29 ` Richard Stallman
2014-01-15 15:52 ` Eli Zaretskii
2014-05-22 20:38 ` bug#16433: Test case for newline cache corruption Ken Olum
2014-05-23 5:50 ` Eli Zaretskii
2014-05-24 8:24 ` Eli Zaretskii
2014-05-26 15:29 ` Ken Olum
2014-05-26 19:28 ` Eli Zaretskii
2014-05-27 15:14 ` Ken Olum
2014-05-27 16:20 ` Ken Olum
2014-05-27 18:04 ` Eli Zaretskii
2014-05-31 10:13 ` Eli Zaretskii
2014-05-31 18:27 ` Eli Zaretskii
2014-06-01 22:30 ` Ken Olum
2014-06-02 2:44 ` Eli Zaretskii
2014-06-05 16:57 ` Ken Olum
2014-06-05 17:31 ` Eli Zaretskii
2014-06-06 15:07 ` Richard Stallman
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=83r48b62ut.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16433@debbugs.gnu.org \
--cc=rms@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.