When I clone this repo `darkBlue` shows up as modified

[jsatk]

If I do a fresh git clone git@github.com:flazz/vim-colorschemes.git && cd vim-colorschemes && git status it shows me this.

On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

    modified:   colors/darkBlue.vim

no changes added to commit (use "git add" and/or "git commit -a")

I've tried the following with no success:

• git checkout -- colors/darkBlue.vim
• git stash && git fetch origin && git reset --hard origin/master
• git mv colors/darkBlue.vim colors/darkblue.vim

All fail.

Any idea why this is? It's borking my plugin manager every time I update.

[jsatk]

This issue relates to or duplicates issues raised in https://github.com/flazz/vim-colorschemes/issues/66 & https://github.com/flazz/vim-colorschemes/issues/122.

[andreis]

Same here. Somehow the case change (colors/darkBlue.vim -> colors/darkblue.vim) messed something up. 🙄

[bradwood]

Same with me -- it's super annoying as the repo remains dirty:

 ~/Code/Dotfiles/config/nvim/plugged  ✔  git clone  https://github.com/flazz/vim-colorschemes.git
Cloning into 'vim-colorschemes'...
remote: Enumerating objects: 1769, done.
remote: Total 1769 (delta 0), reused 0 (delta 0), pack-reused 1769
Receiving objects: 100% (1769/1769), 1.88 MiB | 2.85 MiB/s, done.
Resolving deltas: 100% (579/579), 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:

  'colors/darkBlue.vim'
  'colors/darkblue.vim'
 ~/Code/Dotfiles/config/nvim/plugged  ✔ 

this might shed some light...

Someone with commit rights (@flazz ??) should be able to fix it easily? Will see if I can do a PR in the mean time.

[jsatk]

I think they've abandoned it?

On 02/05, Bradley Wood wrote:

Same with me -- it's super annoying as the repo remains dirty:

~/Code/Dotfiles/config/nvim/plugged  ✔  git clone  https://github.com/flazz/vim-colorschemes.git
Cloning into 'vim-colorschemes'...
remote: Enumerating objects: 1769, done.
remote: Total 1769 (delta 0), reused 0 (delta 0), pack-reused 1769
Receiving objects: 100% (1769/1769), 1.88 MiB | 2.85 MiB/s, done.
Resolving deltas: 100% (579/579), 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:

 'colors/darkBlue.vim'
 'colors/darkblue.vim'
~/Code/Dotfiles/config/nvim/plugged  ✔

this might shed some light...

Someone with commit rights (@flazz ??) should be able to fix it easily? Will see if I can do a PR in the mean time.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/flazz/vim-colorschemes/issues/152#issuecomment-460816623

[jsatk]

This is clearly abandoned.