From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: newline cache
Date: Wed, 23 Apr 2014 01:31:24 -0400 [thread overview]
Message-ID: <E1WcpmG-0000SR-Gp@fencepost.gnu.org> (raw)
In-Reply-To: <838uqxb6o6.fsf@gnu.org> (message from Eli Zaretskii on Tue, 22 Apr 2014 20:44:25 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I investigated what was happening when the bug occurred.
> (forward-line 1) moved across an extra newline, down to point-max.
When forward-line errs, it's too late, because the cache is already
corrupted.
The point is, this is how I know the problem is in the newline cache.
A year ago I debugged the subroutines of Fforward_line and verified
that the problem happened in the call to the newline cache code.
The cache code is in region-cache.c.
I don't have time to study and debug that.
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
Use Ekiga or an ordinary phone call.
next prev parent reply other threads:[~2014-04-23 5:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 16:28 newline cache Richard Stallman
2014-04-21 16:55 ` Eli Zaretskii
2014-04-22 5:37 ` Richard Stallman
2014-04-22 14:28 ` Stefan Monnier
2014-04-22 17:46 ` Eli Zaretskii
2014-04-22 17:44 ` Eli Zaretskii
2014-04-23 5:31 ` Richard Stallman [this message]
2014-04-23 15:14 ` Eli Zaretskii
2014-04-23 5:31 ` Richard Stallman
2014-04-23 15:23 ` Eli Zaretskii
2014-04-24 0:33 ` Richard Stallman
2014-04-25 9:20 ` Eli Zaretskii
2014-04-26 19:58 ` Eli Zaretskii
2014-04-27 2:42 ` Eli Zaretskii
2014-04-29 8:41 ` Jarek Czekalski
2014-04-29 14:25 ` Eli Zaretskii
2014-05-21 8:41 ` Damien Wyart
2014-05-21 13:09 ` Stefan Monnier
2014-05-21 15:30 ` Eli Zaretskii
2014-05-21 15:22 ` Eli Zaretskii
2014-05-21 15:22 ` 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=E1WcpmG-0000SR-Gp@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).