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

Installation issues with vundle and native-vim 8 installer #410

Open
ttxtea opened this issue Jul 2, 2021 · 2 comments
Open

Installation issues with vundle and native-vim 8 installer #410

ttxtea opened this issue Jul 2, 2021 · 2 comments

Comments

@ttxtea
Copy link

ttxtea commented Jul 2, 2021

Is there a way to copy the files into .vim by hand instead of using one of the installer?

I dont get the installers installed, which is not a problem of vim-pandoc. But it would be cool to have a command to just copy the git repo into vim and have it working.

E492: Not an editor command: Plugin 'vim-pandoc/vim-pandoc'
line    2:
E492: Not an editor command: Plugin 'vim-pandoc/vim-pandoc-syntax'
Error detected while processing function vundle#config#bundle[2]..<SNR>18_check_bundle_name:
line    1:
E121: Undefined variable: s:bundle_names
E116: Invalid arguments for function has_key(s:bundle_names, a:bundle.name)
line   11:
E121: Undefined variable: s:bundle_name
@ttxtea
Copy link
Author

ttxtea commented Jul 2, 2021

I think it would be

git clone --depth 1 https://github.com/vim-pandoc/vim-pandoc ~/.vim/pack/plugins/start/vim-pandoc
git clone --depth 1 https://github.com/vim-pandoc/vim-pandoc-syntax ~/.vim/pack/plugins/start/vim-pandoc-syntax

for vim>8 ?

Should this be added to the install instructions?

@alerque
Copy link
Member

alerque commented Jul 2, 2021

Should this be added to the install instructions?

Isn't this just what you'd do for any plugin if you wanted to manually copy it into somewhere? I can think of several reasons to generally recommend using a plugin manager, but for people that want to copy in somewhere themselves there is nothing to stop them, but I don't see why we should be the ones to document that.

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

2 participants