Skip to content

Commit 8e0213e

Browse files
bleachedajimmielyon
authored andcommitted
docs: clarify using opts = {} vs config = function() ... require('plu… (nvim-lua#1316)
* docs: clarify using opts = {} vs config = function() ... require('plugin').setup({}) .. end The current documentation mentioning that using "require" is equivalent to using "opts" without detailing the use in the "config = function()" block seems inaccurate. Lower in the configuration the "config = function()" block is used without clarifying why it needed and what it does. This clarification may help new users understand the difference between the two, or how and where to place the "require" statement. * Update init.lua * remove whitespace
1 parent 39f4deb commit 8e0213e

File tree

1 file changed

+13
-3
lines changed

1 file changed

+13
-3
lines changed

init.lua

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -242,12 +242,22 @@ require('lazy').setup({
242242
-- with the first argument being the link and the following
243243
-- keys can be used to configure plugin behavior/loading/etc.
244244
--
245-
-- Use `opts = {}` to force a plugin to be loaded.
245+
-- Use `opts = {}` to automatically pass options to a plugin's `setup()` function, forcing the plugin to be loaded.
246246
--
247247

248+
-- Alternatively, use `config = function() ... end` for full control over the configuration.
249+
-- If you prefer to call `setup` explicitly, use:
250+
-- {
251+
-- 'lewis6991/gitsigns.nvim',
252+
-- config = function()
253+
-- require('gitsigns').setup({
254+
-- -- Your gitsigns configuration here
255+
-- })
256+
-- end,
257+
-- }
258+
--
248259
-- Here is a more advanced example where we pass configuration
249-
-- options to `gitsigns.nvim`. This is equivalent to the following Lua:
250-
-- require('gitsigns').setup({ ... })
260+
-- options to `gitsigns.nvim`.
251261
--
252262
-- See `:help gitsigns` to understand what the configuration keys do
253263
{ -- Adds git related signs to the gutter, as well as utilities for managing changes

0 commit comments

Comments
 (0)