Fixes #3462 - Change file name casing to fix builds on linux

[dodexahedron]

Fixes

• Fixes #3462

Proposed Changes/Todos

• [X] Rename files for case-sensitive systems

Pull Request checklist:

• [x] I've named my PR in the form of "Fixes #issue. Terse description."
• [ ] My code follows the style guidelines of Terminal.Gui - if you use Visual Studio, hit CTRL-K-D to automatically reformat your files before committing.
• [ ] My code follows the Terminal.Gui library design guidelines
• [x] I ran dotnet test before commit
• [ ] I have made corresponding changes to the API documentation (using /// style comments)
• [x] My changes generate no new warnings
• [x] I have checked my code and corrected any poor grammar or misspellings
  • Literally all I did.
• [ ] I conducted basic QA to assure all features are working

Ready to go whenever. 🤦‍♂️

[dodexahedron]

Critical, for project members to do ASAP

Adding an important note from the issue over here, as well, for everyone to please do ASAP, or at least BEFORE they pull this to their local copies once it's merged (may as well just do it now and be done with it):

git config core.ignorecase false

Without that, you may end up with duplicate files because of casing and the way windows works, and they might even make it back into the repo if certain sequences of not-uncommon actions are performed.

If you do it in your global config, you won't lose the setting if you re-clone on that machine, so it may be a good idea as well:

git config core.ignorecase false --global

[tig]

Critical, for project members to do ASAP

Adding an important note from the issue over here, as well, for everyone to please do ASAP, or at least BEFORE they pull this to their local copies once it's merged (may as well just do it now and be done with it):

git config core.ignorecase false

Without that, you may end up with duplicate files because of casing and the way windows works, and they might even make it back into the repo if certain sequences of not-uncommon actions are performed.

If you do it in your global config, you won't lose the setting if you re-clone on that machine, so it may be a good idea as well:

git config core.ignorecase false --global

This was all working fine before, for years.

Now, after doing this, if I try to checkout another branch, I get

Please advise.

[dodexahedron]

Because that branch has the wrong file names and different settings.

Case sensitivity mismatches SUCK.

Those are the extra files mentioned in the comment above and quoted in the reply.

Delete them. They are extras, because the case was wrong before.

[dodexahedron]

Basically, any way that you take care of it, it will be taken care of for good unless you've got some weird sort of diamond inheritance or something going on that can't be auto-resolved.

But then you still can just delete the wrong-cased files, which are the ones with lower-case build and lower-case shell in Powershell.

Basically, if it says it's untracked, it doesn't care about that file any more. It's just trying to help you in case you actually meant to keep them around.

As for a root cause analysis?

It's my fault, and I think I can trace it back to almost an exact time when I screwed it up, because it was a last-second rename of stuff for consistency, but I missed especially that s vs S in a string vs CLI file listing. My bad.

Again, just delete anything untracked and you're all set. As long as you don't git rm a file that IS in the tree, you're not deleting anything the repo cares about. 👍

And it's honestly pretty annoying that the rename doesn't work like it's supposed to, even though I did explicitly use the git cli to do it in the end, just in case it could make windows behave. But no. Windows gonna Windows.

[dodexahedron]

And if you ever are in a situation with any file anywhere untracked and you're unsure and it's blocking you, just stash them. Then you can carry on and address it later when someone can answer/help/etc.