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
{{ message }}
This repository has been archived by the owner on Apr 16, 2024. It is now read-only.
Users should be able to override a plugins source using a table inside of doom_plugins.lua.
This is important for users who want to use a different fork, or a locally developed version of a plugin.
How would it work
Users should be able to specify a different path that packer will import from. This could live in doom_plugins.lua.
module.plugin_overrides= {
{ 'nvim-treesitter/nvim-tree-docs', 'mygithubaccount/my-nvim-tree-docs-fork' }, -- Use github link
{ 'nvim-treesitter/nvim-tree-docs', '~/projects/nvim_plugins/my-nvim-tree-docs-fork' } -- Use local path
}
Implementation
Then we wrap the packer use function
localwrap_packer=function(packer_use)
returnfunction(spec)
localsource_package=spec[1]
ifutils.has_value(plugin_overrides, source_package) then-- ... replace spec[1] with second value from plugin_overridesspec.commit=nil-- Disable pinned packer dependency endpacker_use(spec)
endendlocaluse=wrap_packer(packer.use)
use({
'nvim-treesitter/nvim-tree-docs',
-- ... config etc
})
This will swap out the packer dependency path for one specified in module.plugin_overrides.
The text was updated successfully, but these errors were encountered:
connorgmeehan
changed the title
[FEATURE] Override doom-nvim dependencies with local/forks
[FEATURE] Override doom-nvim dependencies with local clones or forks
Nov 20, 2021
connorgmeehan
changed the title
[FEATURE] Override doom-nvim dependencies with local clones or forks
[FEATURE] Override doom-nvim packer dependencies with local clones or forks
Nov 20, 2021
Feature Request
Users should be able to override a plugins source using a table inside of doom_plugins.lua.
This is important for users who want to use a different fork, or a locally developed version of a plugin.
How would it work
Users should be able to specify a different path that packer will import from. This could live in
doom_plugins.lua
.Implementation
Then we wrap the packer use function
This will swap out the packer dependency path for one specified in
module.plugin_overrides
.This feature request responds to #181
The text was updated successfully, but these errors were encountered: