Currently, I use vim-plug for managing plugins and vim-colorschemes for my  colorschemes - which doesn't work.Approach 1:in my init.vim:Plug 'flazz/vim-colorschemes'[...]syntax oncolorscheme babymate256set background=darkPutting those colorscheme settings at the end of my init.vim(=after my mappings), works. Putting those before my mappings (but after filetype pluginand that) doesn't. That doesn't make much sense to me, but as neovim supports asynchron execution, that may be the cause.Putting set runtimepath+=~/.dotfiles/nvim/plugged/vim-colorschemes/colors before those colorscheme settings doesn't work either.Approach 2:Putting all colorschemes from nvim/plugged/vim-colorschemes/colors into nvim/colors/ doesn't change anything.Of course, i can set my colorscheme manually after nvim has started.I thought of using just an if structure for setting the colorscheme, but i don't know what i could test, as the colorscheme set doesn't provide any variables.why does the manual configuration using nvim/color doesn't work?Do you have suggestions on how to manage colorschemes?EDIT: I don't like setting it at the end of my file, as it destroys my file structure.
non-default colorschemes can't be loaded; setting them manually after startup works
colorscheme;neovim;startup
Although, i haven't found out what exactly was the problem or how i could solve it in the expected way (just placing colorscheme babymate256 in my config as everyone else does) => i now use just autocmd VimEnter * colorscheme babymate256(which is not as fine as without an autocmd, but it doesn't disorganize up my config structure.)Btw: Additionally, i just haven't found the exact name of my default colorscheme, :colorscheme  had just printed defaultEDITAfterwards, i solved a very similar problem by putting set background=dark before the colorscheme setting.