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
The default (expected) way to handle plugins within one's configuration is to place plugins in a plugins/ RTP directory and check for the existence of the plugin with pcall.
A rocks-config module would allow users to specify per-plugin configuration files (if the plugin is installed and loaded). A global option could also be set which would specify the default directory where files for plugins would be sourced, e.g.:
[plugins]
# plugins go here...
[config]
path = "plugins/"# search in `$CONFIG_DIR/lua/plugins/xyz.lua` for each installed plugin
The text was updated successfully, but these errors were encountered:
The default (expected) way to handle plugins within one's configuration is to place plugins in a
plugins/
RTP directory and check for the existence of the plugin withpcall
.A
rocks-config
module would allow users to specify per-plugin configuration files (if the plugin is installed and loaded). A global option could also be set which would specify the default directory where files for plugins would be sourced, e.g.:The text was updated successfully, but these errors were encountered: