You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.The text was updated successfully, but these errors were encountered: