> Is the behavior consistently reproducible?
Unfortunately, no. Since it happened twice this morning, it has yet to happen again.
> Under the Help menu, choose About SourceGear Vault. The resulting dialog box says "Version 3.0.6 (2856)", right?
> What kind of file system are you using? For example, is it NTFS on a local drive? Is it a remote mounted file system? Is it Samba?
NTFS on a local hard drive which is split into two logical drives (C and D), on a Dell Latitude running WinXP SP1.
> Are you editing just one file and it doesn't show up in the pending change set? Or are you editing more than one? How many?
Just one file, maybe two. Never a lot.
> What version of emacs? I doubt this matters, but I thought I would ask. I just tried editing a file with emacs 21.3, and it worked fine.
21.3.1. And I just tried again and it worked fine for me too. I also made this happen with BCB6.
> Under the Tools menu, choose Options, and click to the "Concurrent Development Style" page. What is the state of the "Require Check Out Before Check In" checkbox? It should be unchecked, right?
> What version of Windows is being used on the client machine?
Windows XP Service Pack 1
> What CPU is in that machine?
2.2 GHz Intel Pentium 4M
> How much RAM?
> Does your client logfile (%TEMP%\VaultGuiClient.txt) contain anything unusual around the time of the problem? If .NET's FileSystemWatcher class overflows its internal buffer, Vault should report this to the log.
No such file in my %TEMP% directory.
> Check your Event Viewer as well, as this error may have been reported there instead if anything went wrong trying to write to the log file.
No luck there either. Not a single Vault message.
> Was the offending file in the currently selected folder? It sounds like it was, since you said the status was Edited, and that suggests that you had its folder open to check that status.
The file was not in the currently selected folder while I was editing it. After I was finished and had saved my changes, I had to navigate to the folder in order to check it in. Doing a file diff, history, or opening and closing the Options menu will all make the file pop onto the Pending Change List.
> If you switch away to another app and then switch back, does the file show up in the pending change set?
I'm pretty sure it doesn't, but I will try again next time it happens.
> If you quit the Vault client and open it again, does the file show up in the pending change set?
I'm pretty sure it does, but again, I will try again next time it happens.
> If you right-click on the folder containing the file and choose Check In, does the file show up in the resulting dialog?
In the first version of Vault that we had, you were unable to check it in. Vault would flicker and then pretend like nothing had happened (not even a message in the Messages tab). In the next version (3.0?), this would make the file appear in the pending change list, and you could check it in.
> Did this problem happen just after the client started up?
> (When the client starts up, it performs a scan of your working folder. If your working folder contains lots of files, this scan can take a minute or so. Until the scan completes, the file may not show up in the pending change set.)
> Or are you saying that you modified a file with the Vault client already running and the Vault client failed to notice the change?
It was running when I started editing, and was untouched until after I was finished editing.