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

ScriptType #19

Open
athos-ribeiro opened this issue Jan 24, 2015 · 2 comments
Open

ScriptType #19

athos-ribeiro opened this issue Jan 24, 2015 · 2 comments

Comments

@athos-ribeiro
Copy link
Contributor

Whenever a plugin has no script type defined, Vimana does not know what to do with it.

Since many of the recent plugins just try to support pathogen whenever they are developed, they do not care about setting a type anymore. How should we address that? Should we just add the type to every project we want to support, or should we check for the project directory tree, and if they are pathogen compatible, distribute them according to the directory tree?

e.g.: If foobar project has a foobar/syntax/syntax.vim file, we could assume this is a syntax plugin.

@c9s
Copy link
Owner

c9s commented Jan 27, 2015

Sure, I think it works. It would be great if you have any PR for this, I am glad to accept the patch. :)

@athos-ribeiro
Copy link
Contributor Author

Definitely! I will write one this week, I created the issue 1st just to
make sure it was a good idea :)
Em 27/01/2015 11:39, "Yo-An Lin" [email protected] escreveu:

Sure, I think it works. It would be great if you have any PR for this, I
am glad to accept the patch. :)


Reply to this email directly or view it on GitHub
#19 (comment).

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