Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Is it possible to make the plugin compatible with pack/plugins/start? #335

Open
harrypotterIUP opened this issue Sep 27, 2024 · 0 comments

Comments

@harrypotterIUP
Copy link

harrypotterIUP commented Sep 27, 2024

❤️ Thanks for your work on this plugin! It'd be awesome if it would be possible to make it compatible with the vim system I'm on.

I did read the installation instructions regarding this plugin requiring to be set up in ~/.vim/pack/*/opt/. Unfortunately however, on my system, the plugins indiscriminately sit in pack/plugins/start, ergo ~/.vim/pack/plugins/start/onedark.vim. This results in a long, long list of errors on start-up when setting onedark as the colorscheme. By searching for those errors, I found a related previous issue thread #164.

  • Putting colorscheme onedark in the last line of vimrc didn't resolve the issue.
  • Replacing colorscheme onedark with a timer call timer_start(1, {-> execute("colorscheme onedark")}) does work, but results in a (subjective?) delay/start-up time and some ugly reformatting/recoloring every time a file is opened.
  • Using autocmd VimEnter * colorscheme onedark has some effects but somehow conflicts with lightline in the sense that it is completely colorless (independent from chosen lightline colorscheme) and is only fixed by running :colorscheme onedark again, manually.
  • If using autocmd VimEnter * ++nested colorscheme onedark instead, the commandline/statusline gets cleared on start-up, instead of showing information about the opened file.
  • There was another solution mentioned in the other thread that it would be possible to fix the issue by moving code, but I couldn't make that work, unfortunately.

Is there another solution to make onedark.vim more compatible with other plugin folder structures? Thank you very much in advance for any pointers.

In case it's relevant I'm on the most recent commit 390b893 and my vim is 8.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant