vs-chromium indexing fails (and has always failed) on my main chromium client. The indexer seems to choke on some invalid ntfs junction points that szager tells me might be left around from a time when this client was using the submodules workflow.
I could clean the junk up, but I think it's better to teach vs-chromium to ignore the errors, since it might occur on other clients too. I have a patch ready.
vs-chromium indexing fails (and has always failed) on my main chromium client. The indexer seems to choke on some invalid ntfs junction points that szager tells me might be left around from a time when this client was using the submodules workflow.
I could clean the junk up, but I think it's better to teach vs-chromium to ignore the errors, since it might occur on other clients too. I have a patch ready.