Skip to content

Commit

Permalink
Merge pull request #414 from mrjones2014/bot/vimdoc/master
Browse files Browse the repository at this point in the history
chore: generated vimdoc
  • Loading branch information
mrjones2014 authored Oct 19, 2023
2 parents a4a394c + f979bb8 commit 6ea46c2
Showing 1 changed file with 7 additions and 3 deletions.
10 changes: 7 additions & 3 deletions doc/legendary-extensions.txt
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
*legendary-extensions.txt* Last change: 2023 October 10
*legendary-extensions.txt* Last change: 2023 October 11

==============================================================================
Table of Contents *legendary-extensions-table-of-contents*
Expand Down Expand Up @@ -93,15 +93,19 @@ Automatically load key mappings defined in lazy.nvim
require('legendary').setup({
extensions = {
lazy_nvim = true,
}
},
})
<


`WHICH-KEY.NVIM` *legendary-extensions-which-key.nvim*

Automatically load key mappings defined by which-key.nvim
<https://github.com/folke/which-key.nvim> into `legendary.nvim`.
<https://github.com/folke/which-key.nvim> into `legendary.nvim`. For
`auto_register` to work, `which-key.nvim` must be loaded on `runtimepath`
before `legendary.nvim` initializes, but `legendary.nvim` must initialize the
extension before `require('which-key').register()` is called. Alternatively,
you can just pass your `which-key` tables to `legendary` directly.

>lua
require('legendary').setup({
Expand Down

0 comments on commit 6ea46c2

Please sign in to comment.