[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: newline cache
From: |
Eli Zaretskii |
Subject: |
Re: newline cache |
Date: |
Wed, 23 Apr 2014 18:14:31 +0300 |
> Date: Wed, 23 Apr 2014 01:31:24 -0400
> From: Richard Stallman <address@hidden>
> CC: address@hidden
>
> > 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.
I don't doubt that. An even easier way to make sure is set
cache-long-scans to a nil value.
> The cache code is in region-cache.c.
>
> I don't have time to study and debug that.
That's okay, I just mentioned that for if/when you will.
- newline cache, Richard Stallman, 2014/04/21
- Re: newline cache, Eli Zaretskii, 2014/04/21
- Re: newline cache, Richard Stallman, 2014/04/23
- Re: newline cache, Eli Zaretskii, 2014/04/23
- Re: newline cache, Richard Stallman, 2014/04/23
- Re: newline cache, Eli Zaretskii, 2014/04/25
- Re: newline cache, Eli Zaretskii, 2014/04/26
- Re: newline cache, Eli Zaretskii, 2014/04/26
- Re: newline cache, Jarek Czekalski, 2014/04/29
- Re: newline cache, Eli Zaretskii, 2014/04/29