Re: Commit mistake?

[Stephen Berman <stephen.berman@gmx.net>]

On Sun, 25 Nov 2018 13:16:35 -0500 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:

>> I used VC.  The file was listed in *vc-dir*, but it has been for ages
>> and was never a problem before.
>
> Hmm... IIUC it was there because it's a file we used to generate but we
> don't generate any more, so it's not ignored by .gitignore any more
> (i.e. you should just `rm` it).

Yes, I've since done that.

> I recommend you don't ignore files marked as "unknown" in *vc-dir*:
> they're a sign that there's a problem somewhere and it should be fixed
> either by removing the file, or renaming it, or by changing .gitignore.

Thanks, I'll bear that in mind.

>> But this time after I committed the change the status of that file
>> also changed to "up-to-date", which suprised me but, unfortunately,
>
> Do you remember exactly how you caused the commit?  I guess you used `v`
> in *vc-dir*, but did you first select the files you wanted to commit, or
> did you rely on the position of point to specify the file(s) (maybe
> with point placed on a directory)?

I'm pretty sure I marked only the file I wanted to commit and then typed
`v' -- that's what I habitually do -- but I can't categorically rule out
that I may have just typed `v' without marking.  I also don't recall
seeing the unwanted file in the list of files shown when editing the
commit message, but here too, I may have overlooked it.

Steve