From 0a34571e4996405b956de8e3d25ce42d66d0ef54 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Wed, 14 Dec 2022 20:58:18 +0000 Subject: [PATCH] chore(build): auto-generate vimdoc --- doc/lazy.nvim.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/lazy.nvim.txt b/doc/lazy.nvim.txt index 8646980..a98b330 100644 --- a/doc/lazy.nvim.txt +++ b/doc/lazy.nvim.txt @@ -7,10 +7,10 @@ Table of Contents *lazy.nvim-table-of-contents* - Features |lazy.nvim-features| - Requirements |lazy.nvim-requirements| - Installation |lazy.nvim-installation| - - Usage |lazy.nvim-usage| - Configuration |lazy.nvim-configuration| + - Usage |lazy.nvim-usage| - Profiler |lazy.nvim-profiler| - - Debug |lazy.nvim-debug| + - 🪲 Debug |lazy.nvim-🪲-debug| - Differences with Packer |lazy.nvim-differences-with-packer| - Other Neovim Plugin Managers in Lua|lazy.nvim-other-neovim-plugin-managers-in-lua| @@ -71,9 +71,7 @@ You can use the following Lua code to bootstrap **lazy.nvim** < -USAGE *lazy.nvim-usage* - -Add **lazy.nvim** to the top of your `init.lua` +Next step is to add **lazy.nvim** to the top of your `init.lua` > -- You can use a lua module that contains your plugins. @@ -175,6 +173,8 @@ CONFIGURATION *lazy.nvim-configuration* < +USAGE *lazy.nvim-usage* + PROFILER *lazy.nvim-profiler* The profiling view shows you why and how long it took to load your plugins. @@ -184,7 +184,7 @@ The profiling view shows you why and how long it took to load your plugins.

image

-DEBUG *lazy.nvim-debug* +🪲 DEBUG *lazy.nvim-🪲-debug* See an overview of active lazy-loading handlers and what’s in the module cache