Hello,
Eric Abrahamsen writes:
> Nicolas Goaziou writes:
>> The corrupted element is only interesting when there's a pattern (e.g.
>> only lists and items are corrupted). Another important information is
>> the action triggering the corruption. The function helps to find it out.
>
> Ah, so you
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> Yes, it's up to date -- after I sent this message I started wondering
>> if it had been a while since I updated, so I pulled and reloaded, and
>> not long after that saw the bug again.
>
> Well, too bad.
>
>> I expect to see this
Hello,
Eric Abrahamsen writes:
> Yes, it's up to date -- after I sent this message I started wondering
> if it had been a while since I updated, so I pulled and reloaded, and
> not long after that saw the bug again.
Well, too bad.
> I expect to see this again, so I can run the function above,
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> While editing a plain list yesterday I noticed what I guess was a bug in
>> the caching mechanism.
>
> It looks like it, indeed.
>
>> The list item was wrapped to several lines, and I noticed that calling
>> C-e while on the last
Hello,
Eric Abrahamsen writes:
> While editing a plain list yesterday I noticed what I guess was a bug in
> the caching mechanism.
It looks like it, indeed.
> The list item was wrapped to several lines, and I noticed that calling
> C-e while on the last line gave me "wrong-type-argument
> inte
While editing a plain list yesterday I noticed what I guess was a bug in
the caching mechanism.
The list item was wrapped to several lines, and I noticed that calling
C-e while on the last line gave me "wrong-type-argument
integer-or-marker-p nil". Trying to fill the item with M-q gave me
"user-er
