You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the one hand this looks like a minor annoyance as it duplicates content.
For Windows users (maybe Mac? Unclear about this) this is even more annoying due to the use of a file system that will retain case BUT it is essentially case-less, this then leads to an inaccessible file and warnings from git:
C:\code\terminal>git clone https://github.com/eylles/pywal16.git
Cloning into 'pywal16'...
remote: Enumerating objects: 5580, done.
remote: Counting objects: 100% (421/421), done.
remote: Compressing objects: 100% (198/198), done.
Receiving objects: 100% (5580/5580), 872.64 KiB | 1.47 MiB/s, done. 5159 (from 1)Receiving objects: 100% (5580/5580), 724.01 KiB | 1.38 MiB/s
Resolving deltas: 1% (35/3482)
Resolving deltas: 100% (3482/3482), done.
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'pywal/templates/Colors.hs'
'pywal/templates/colors.hs'
@threadreaper and @eylles thoughts? I'm happy to open a PR if this sounds reasonable. I'm not using these so whilst I'm confident this is a reasonable plan, it won't impact me negatively if it's a terrible idea 😆
The text was updated successfully, but these errors were encountered:
See
On the one hand this looks like a minor annoyance as it duplicates content.
For Windows users (maybe Mac? Unclear about this) this is even more annoying due to the use of a file system that will retain case BUT it is essentially case-less, this then leads to an inaccessible file and warnings from git:
Checking code:
I think we can remove one, and update the code to use the same filename.
My recommendation is to remove the Uppercase one, Colors.hs added 2022 in change b473c5a by @threadreaper
Retaining the 2018 change fd6820d
@threadreaper and @eylles thoughts? I'm happy to open a PR if this sounds reasonable. I'm not using these so whilst I'm confident this is a reasonable plan, it won't impact me negatively if it's a terrible idea 😆
The text was updated successfully, but these errors were encountered: