From 1fc4c26789e862e7b56f062b99f0aecf27b28ba2 Mon Sep 17 00:00:00 2001 From: NotAShelf Date: Fri, 28 Jul 2023 09:23:51 +0000 Subject: [PATCH] deploy: a7a4f8eba88dedf5a9ac0f87ef7888c0fb57e6be --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index d515470e..a3288bc2 100644 --- a/index.html +++ b/index.html @@ -41,7 +41,7 @@ $ nix run github:notashelf/neovim-flake#maximal

Chapter 4. Custom Plugins

You can use custom plugins, before they are implemented in the flake. To add a plugin, you need to add it to your config’s config.vim.startPlugins array.

4.1. New Method

As of version 0.5, we have a more extensive API for configuring plugins, under vim.extraPlugins.

Instead of using DAGs exposed by the library, you may use the extra plugin module as follows:

{
-  config.vim.extraPlugins = with pkgs.vimPlugins; {
+  config.vim.extraPlugins = with pkgs.vimPlugins; [{
     aerial = {
       package = aerial-nvim;
       setup = ''
@@ -57,7 +57,7 @@ To add a plugin, you need to add it to your config’s con
       after = ["aerial"];
     };
   };
-}

4.2. Old Method

Users who have not yet updated to 0.5, or prefer a more hands-on approach may use the old method where the load orderof the plugins is determined by DAGs.

{
+}]

4.2. Old Method

Users who have not yet updated to 0.5, or prefer a more hands-on approach may use the old method where the load orderof the plugins is determined by DAGs.

{
   # fetch plugin source from GitHub and add it to startPlugins
   config.vim.startPlugins = [
     (pkgs.fetchFromGitHub {