name/file conflicts megathread

[flazz]

Hey all, first of all, thanks for the patience. There seems to be a large set of issues that revolves around the filename conflicting with some internal value or vim feature.

I think biggest challenge is that there are many flavors of this issue and many flavors of proposed solutions. Solving one issue may conflict with solving another.

Instead of modifying the scheme files to for any specific situation we start sharing a set of opt-in scripts to fix these things locally.

If any convergence happens we can work towards a better general case solution; if things stay diverged no harm done, the impact is a set of scripts and words in the readme. Thoughts?

[peara]

Hi, the issue with conflicting name was when I set color scheme to one with a wrongly name (different with its file or same as another's). Next time when vim starts up, it will take the wrong one, or cannot find any. So I guess it must be fixed. At least the name of the scheme and the file contains it must be the same.

[Knio]

I'm very 👎 on scripts and additional instructions. The files should simply work as advertised out of the box.

I'm not an expert or even a mediocre user of vim to even be sure if I understand the issue, so someone else can please correct me, but it seems like the file name on the filesystem has the match the scheme name declared inside the file. So it's a pretty simple two choices: either rename the file, or rename the scheme (or both, as long as they match, or tell me I misunderstood the issue). I have no opinion on which solution is chosen, or how these files or names came to be.

[chris-roerig]

My vote is for convention over configuration. Renaming all existing themes to lowercase and then only accepting lowercase themes after that would solve the issue.