|author||Tom Ryder <email@example.com>||2018-05-31 18:16:05 +1200|
|committer||Tom Ryder <firstname.lastname@example.org>||2018-05-31 18:16:05 +1200|
Rebuild dotfiles(7) manual from source
1 files changed, 10 insertions, 6 deletions
diff --git a/man/man7/dotfiles.7df b/man/man7/dotfiles.7df
index 046e35db..a30d0028 100644
@@ -490,12 +490,19 @@ structures like functions, I like to implement it as a plugin in
\f[C]~/.vim/plugin\f and/or \f[C]~/.vim/autoload\f.
There's documentation for each of those in \f[C]~/.vim/doc\f.
-Any/all of those plugins may eventually be spun off into their own
-repositories in the future, but for the moment they live here.
-You can create distribution packages for them with
+They eventually get either discarded or spun off into their own
+repositories, added to this repository as submodules intead, and
+You can create distribution packages for whatever's still in here with
\f[C]make\ dist\-vim\-plugin\f; they will be created in
+All plugins and colorschemes with their own repositories are installed
+as submodules in \f[C]~/.vim/bundle\f.
+They are installed into \f[C]~/.vim\f as normal.
I also define a few rules specific to file types I often edit in
\f[C]~/.vim/after/ftplugin\f, including some local mappings for
checking, linting, and tidying, and a few more in
@@ -503,9 +510,6 @@ checking, linting, and tidying, and a few more in
There are also a few tweaks to core syntax files in
\f[C]~/.vim/after/syntax\f, especially for shell script
-Third\-party plugins are in submodules in \f[C]~/.vim/bundle\f.
-They are installed into \f[C]~/.vim\f as normal.
I test my configuration every now and then with the Neovim