IDE issue

[John Z]

Pelle said
"If the problem relates to the Integrated Environment (IDE), try to provide step-by-step instructions how to reproduce the problem. I can't guess what you did. If you don't know - I don't know. A screenshot will almost always help, but is usually not enough by itself..."

So here is an issue I can't create at will,  I do not know how it happens or what I do to cause it.  It is easily fixable by deleting the .tag file.  So I'm not saying bug 

The source file panel doubles the file entries shown in the first image.  The second image shows that the filename has not changed yet below that it shows when I select the source file a window to resolve the 'issue'.

I attached the .tag file which contains the doubled names with case change.

I never posted before because I can't reproduce at will, a primary necessity for a bug report.  Has been something weird that I do, I guess, as far back as at least V11 or further back.

SO - Just in case anyone else has observed this and are able to reproduce 'at will'.

John Z

[Pelle]

AFAIK, all tools will pick up the exact spelling of a filename. If the .tag database contains "DBSearch.c" and "dbsearch.c", both spellings must have been present on your disk at some point.

Can you remember renaming this file, and if it was done from the IDE or from Windows (Explorer / Command line / whatever)?

[John Z]

Thanks Pelle,

It's an idea. I'm sure at some point I've renamed a file but not to just change case I think.  Also Windows does not distinguish case in the file name, I believe. 

I'll run a few test along this line of thinking though.

John Z

[Robert]

Hi John Z:

Maybe relevant, check this out.

https://www.howtogeek.com/354220/how-to-enable-case-sensitive-folders-on-windows-10/

[Pelle]

John Z,

What I'm trying to say is that I never "normalize" a filename, never turn "TEST.C" into "test.c" or something like that. I use the exact spelling returned from functions like FindFirstFile*() / FindNextFile*(). The fact that you have two different spellings means your directory at one point must have contained "DBSearch.c" and at another point must have contained "dbsearch.c". This is a fact (and that Windows can match "TeSt.C" with the name "test.c" stored in the directory is irrelevant).

It seems most likely that it was a user action that renamed "dbsearch.c" into "DBSearch.c", or vice versa. But you are closer to this possible action...

[John Z]

Thanks Pelle, I'll watch closely from now on. It is not frequent. If I ever can intentionally make it happen I'll post again.

Thanks Robert - I do prefer case insensitive though.

John Z