bug#7905: 24.0.50; VC not updating file status properly anymore after commit from vc-dir

[Tim Van Holder <tim.vanholder@gmail.com>]

On 26 January 2011 10:44, Tim Van Holder <tim.vanholder@gmail.com> wrote:
> On 26 January 2011 05:25, Glenn Morris <rgm@gnu.org> wrote:
>> Tim Van Holder wrote:
>>
>>> By a process of elimination, it turns out that the
>>>   '(display-time-mode t)
>>> line in (custom-set-variables) is the culprit. With that removed,
>>> things work, even without --no-splash.
>>>
>>> I'm attaching a tarball with a dummy CVS repos; my tests used:
>>
>> Thanks for the great test case, but I'm afraid I still cannot
>> reproduce it if I use a .emacs that just has a customized
>> display-time-mode (together with --no-site-file).
>>
>> Does anyone else see this problem?
>
> That's odd - using the testcase, if I do
>
>  $ emacs -Q
>  [C-x v d]sandbox
>  n
>  M
>  [M-x]display-time-mode
>  v
>  foo[C-c C-c]
>
> then the files go to "edited" for me (without the display-time-mode
> they become "up-to-date").
> Would it help for me to edebug particular VC defuns to see where
> exactly things go wrong?

It seems to run deeper than just commits. I'm seeing now that any
CVS-controlled file I visit is marked as "CVS:1.x" (i.e. edited), even
files in a freshly checked out sandbox. [C-x v u] clears that state,
but saving the file, closing it and then revisiting it puts it in
edited state again.
I'm reasonably sure that didn't happen before; however, files are only
showing up in vc-dir if they are actually changed, so I may just have
missed this. This behaviour does not go away when I disable
display-time-mode, however, so it could be a completely separate
issue.