unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Wed, 15 Jan 2014 17:52:32 +0200	[thread overview]
Message-ID: <83ppnt44zj.fsf@gnu.org> (raw)
In-Reply-To: <E1W3Paj-0006bR-W9@fencepost.gnu.org>

> Date: Wed, 15 Jan 2014 07:29:05 -0500
> From: Richard Stallman <rms@gnu.org>
> CC: 16433@debbugs.gnu.org
> 
>     To reproduce it at that time, do you happen to remember what sequence
>     of commands was needed?
> 
> (mail-fetch-field "X-RMAIL-ATTRIBUTES") reproduced the bug, when it
> was happening.

Thanks.

>     If and when it happens again, please try to look for editing
>     operations that change buffer text (insert or delete characters), but
>     do not invalidate the cache for the region where characters were
>     inserted or deleted.
> 
> I had not done any manual editing on the RMAIL buffer.
> It was operated on by Rmail commands.  If you see what editing
> functions they call, you will see what I did to the RMAIL buffer.

I meant editing operations that Rmail invokes behind the scenes, like
when it displays a message in rmail-view-buffer.

> It's possible I decrypted it with rmail-epa-decrypt.

Thanks, I'll take a look at that.

> If it isn't obvious what is wrong, we need to fix this bug somehow.  I
> am thinking of turning off the newline cache in Rmail mode.

That'd sweep the problem under the carpet, so I don't recommend that,
not yet anyway.





  reply	other threads:[~2014-01-15 15:52 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
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 [this message]
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

  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=83ppnt44zj.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 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).