|author||Tom Ryder <email@example.com>||2018-06-06 18:04:24 +1200|
|committer||Tom Ryder <firstname.lastname@example.org>||2018-06-06 18:04:24 +1200|
|parent||Bump VERSION (diff)|
Rebuild dotfiles(7) manual page
1 files changed, 19 insertions, 6 deletions
diff --git a/man/man7/dotfiles.7df b/man/man7/dotfiles.7df
index c215ae80..6960e3c5 100644
@@ -477,12 +477,17 @@ The majority of the Vim configuration is just setting options, with a
I try not to deviate too much from the Vim defaults behavior in terms of
interactive behavior and keybindings.
-The configuration is broken into smaller files in
-\f[C]~/.vim/config/*.vim\f, included by \f[C]~/.vimrc\f using
It's extensively commented, mostly because I was reading through it one
day and realized I'd forgotten what half of it did.
+System\-specific configuration files go in \f[C]~/.vim/config\f.
+I define my own \f[C]filetype.vim\f and \f[C]scripts.vim\f, so that
+filetype detection works in a way I like, and loads quickly.
+They are very unlikely to suit you as they are, but you might be able to
+extend them with your favourite filetypes.
+If you delete both of them from \f[C]~/.vim\f, you'll get the stock
+filetype detection back.
If the logic for doing something involves more than a few lines or any
@@ -501,6 +506,14 @@ All plugins and colorschemes are available as submodules in
They are installed into \f[C]~/.vim\f.
+I still use two third\-party plugins: Tim Pope's
+repeat.vim (https://www.vim.org/scripts/script.php?script_id=2136) and
+In my opinion, these plugins are so fundamental and useful that they
+should have been implemented in or bundled with Vim itself many years
+.SS Filetype plugins
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
@@ -508,8 +521,8 @@ 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
-Some/all of these filetype plugins are also due to be separately
-distributed and installed via submodules instead.
+Some of these filetype plugins are also due to be separately distributed
+and installed via submodules instead.
I test my configuration every now and then with the Neovim