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

The renderers installed with Hammer should be separate from user-defined renderers. #40

Open
ghost opened this issue Mar 17, 2012 · 4 comments

Comments

@ghost
Copy link

ghost commented Mar 17, 2012

Right now, renderers are found through Hammer::ENV.renderers_path, which points at $INSTALL_DIR/renderers.
This is bad, though, because when a user wants to add a custom renderer to a location of their choice(outside $INSTALL_DIR) they will lose renderers that hammer adds to render markdown, HTML, and POD documents (all of which reside in $INSTALL_DIR/renderers). I'm open to suggestions for a solution.

@ghost
Copy link
Author

ghost commented Mar 17, 2012

This is true for commands also.

@wikimatze
Copy link
Owner

An idea would be to setup an options which enables the user to take a custom folder like $MYVIMRC/hammer_custom_render which will be taken instead of the default renderers by the plugin?

@ghost
Copy link
Author

ghost commented May 2, 2012

Yes, something like that could work, I think we need to separate system renderers (those owned by hammer) and user renderers(those owned by the user).

@wikimatze
Copy link
Owner

Got it.

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

1 participant