-
Notifications
You must be signed in to change notification settings - Fork 26
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
scvim fails to start with nvim #59
Comments
nvim
Yeah that shouldn't be hardcoded like that, and the error message also needs to be more helpful. The trivial fix is to also hardcode neovim's default directory, but that would be kind of lame (but certainly workable). I'd much prefer to have something based on vim's runtimepath setting, as written about over on superuser, but if it isn't straight forward to implement hardcoding's fine. |
Hm the runtimepath seems to be a list of comma separated paths, so we can just |
I have a branch that I'm using with neo vim and a pull request for it. It requires that you point supercollider at the I'll either want to setup supercollider to ignore the I'm thinking, maybe it doesn't make sense to include SCVim with supercollider. It is easy enough to install with one of the various package managers and, scvim could pass an argument to |
Any updates on this one? I would love to use these together 🙏 |
When starting from
nvim
, scvim fails sto initialize because it doesn't find a.vim
folder, sincenvim
uses the.config/nvim
folder.This can be easily fixed by the user by symlinking
~/.config/nvim
to.vim
, but the error message is very unhelpful:since the readme doesn't mention anything about needing
scvim
to be on the.vim
folder.I suggest either changing the error message to something more specific or adding a line or two in the README making it clear that scvim needs to be in the
~/.vim
folderThe text was updated successfully, but these errors were encountered: