When re-saving a file that has no unsaved changes in VS Code, then RTags still reindexes the file automatically by default, but the VS Code extension does not get an opportunity to pass unsaved changes to other files to RTags. If RTags does not receive any unsaved changes when it reindexes a file, then it seems to assume that there are no unsaved changes to any files, and reverts to the last saved versions of the files. Therefore, any unsaved changes to files besides the one being reindexed are lost.
When re-saving a file that has no unsaved changes in VS Code, then RTags still reindexes the file automatically by default, but the VS Code extension does not get an opportunity to pass unsaved changes to other files to RTags. If RTags does not receive any unsaved changes when it reindexes a file, then it seems to assume that there are no unsaved changes to any files, and reverts to the last saved versions of the files. Therefore, any unsaved changes to files besides the one being reindexed are lost.