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

scvim fails to start with nvim #59

Open
claudiocabral opened this issue Oct 3, 2019 · 6 comments
Open

scvim fails to start with nvim #59

claudiocabral opened this issue Oct 3, 2019 · 6 comments

Comments

@claudiocabral
Copy link
Contributor

When starting from nvim, scvim fails sto initialize because it doesn't find a .vim folder, since nvim 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:

SCVim could not be initialized. Consult the README to see how to install scvim.

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 folder

@claudiocabral claudiocabral changed the title scvim doesn't fails to start with nvim scvim doesn't fails to start with nvim Oct 3, 2019
@claudiocabral claudiocabral changed the title scvim doesn't fails to start with nvim scvim fails to start with nvim Oct 3, 2019
@capocasa
Copy link
Member

capocasa commented Nov 6, 2019

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.

@claudiocabral
Copy link
Contributor Author

Hm the runtimepath seems to be a list of comma separated paths, so we can just split(runtimepath, ",") and iterate through it until we find something that works.
Again, seems easy enough. I'll give it a shot

@x37v
Copy link
Contributor

x37v commented Mar 15, 2020

I have a branch that I'm using with neo vim and a pull request for it.
#64

It requires that you point supercollider at the sc directory inside your scvim checkout.. and in turn the SCVim.sc class looks for the bin etc in the directory above it.

I'll either want to setup supercollider to ignore the SCVim.sc that can be included with it, simply don't build with scvim support or delete the SCVim.sc from the appropriate dir.

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 sclang when starting to point it at the correct location for the SCVim.sc class file..

@lpil
Copy link
Contributor

lpil commented Aug 13, 2020

Any updates on this one? I would love to use these together 🙏

@capocasa
Copy link
Member

@lpil PR is closed by creator. @x37v can you do a minimal port of your fix to master?

@x37v
Copy link
Contributor

x37v commented Aug 14, 2020

@lpil PR is closed by creator. @x37v can you do a minimal port of your fix to master?

@capocasa yeah, i'll try to get to this soon

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

No branches or pull requests

4 participants