aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2019-06-16 18:06:53 +1200
committerTom Ryder <tom@sanctum.geek.nz>2019-06-16 18:06:53 +1200
commitd326ddede3968a569f71830ea2927bdd798a1139 (patch)
treefa4707d7fa6c17a3490a657a9bacf6658ddfa824
parentMerge branch 'release/v6.19.0' (diff)
parentBump VERSION (diff)
downloaddotfiles-d326ddede3968a569f71830ea2927bdd798a1139.tar.gz
dotfiles-d326ddede3968a569f71830ea2927bdd798a1139.zip
Merge branch 'release/v6.20.0'v6.20.0
* release/v6.20.0: Add 'foldlevel' setting maps
-rw-r--r--VERSION4
-rw-r--r--vim/vimrc9
2 files changed, 11 insertions, 2 deletions
diff --git a/VERSION b/VERSION
index 312b8260..67ae0149 100644
--- a/VERSION
+++ b/VERSION
@@ -1,2 +1,2 @@
-tejr dotfiles v6.19.0
-Sun, 16 Jun 2019 05:55:33 +0000
+tejr dotfiles v6.20.0
+Sun, 16 Jun 2019 06:06:53 +0000
diff --git a/vim/vimrc b/vim/vimrc
index 1273840f..5d12b321 100644
--- a/vim/vimrc
+++ b/vim/vimrc
@@ -1564,6 +1564,15 @@ xmap <Leader>r <Plug>(ReplaceOperator)
nmap <Leader>* <Plug>(RegexEscape)
xmap <Leader>* <Plug>(RegexEscape)
+" I don't have anything for which I'm using the numbers just yet, so let's set
+" them to apply an explicit 'foldlevel' for now, which is occasionally useful,
+" though I suspect I'm more likely to keep using zM, zm, and zr.
+"
+for s:key in range(0,9)
+ execute 'nnoremap <Leader>'.s:key.' :<C-U>set foldlevel='.s:key.'<CR>'
+ execute 'xmap <Leader>'.s:key.' <Esc><Leader>'.s:key.'gv'
+endfor
+
" And last, but definitely not least, I'm required by Vim fanatic law to
" include a mapping that reloads my whole configuration. This uses the
" command wrapper defined much earlier in the file, so that filetypes also get