Subject: bug#23823: 25.0.95; Reset between highlight buffer/file comparisons

From: Tino Calancha <[email-masked]>
Date: Fri, 24 Jun 2016 13:36:17 +0900 (JST)

On Thu, 23 Jun 2016, Eli Zaretskii wrote:

>> Cc: [email-masked]
>> From: Tino Calancha <[email-masked]>
>> Date: Thu, 23 Jun 2016 09:46:27 +0900
>>
>> My point is: why don't we perform a fresh comparison in 2?
>
> Because the first time you call highlight-compare-with-file, it turns
> on the highlight-changes-mode, which begins to mark changes, including
> the replacement of 'b' with 'f'.
Yeah, that sounds nice to me: the user is still somehow in the context 
of the first func. call.

> Why does it make sense to forget all  that information?
Because the user called the function again: this may start a new context, 
i.e., reset the minor mode in that buffer.

I imagine buf-a becaming a mess of colors with all those changes around. 
At some point the user may want to compare again the current status of 
buf-a with file-b.