diff options
author | Tom Ryder <tom@sanctum.geek.nz> | 2019-06-19 15:24:01 +1200 |
---|---|---|
committer | Tom Ryder <tom@sanctum.geek.nz> | 2019-06-19 15:24:01 +1200 |
commit | 352e2b820167ff2377350683a88a69af803be78c (patch) | |
tree | dd579c6f2170b8dcb5191101c69f97e0d6e12206 /vim/vimrc | |
parent | Inline option resets and undos in Vim C ftplugin (diff) | |
download | dotfiles-352e2b820167ff2377350683a88a69af803be78c.tar.gz dotfiles-352e2b820167ff2377350683a88a69af803be78c.zip |
Move 'foldmethod' definitions out to filetypes
Diffstat (limited to 'vim/vimrc')
-rw-r--r-- | vim/vimrc | 18 |
1 files changed, 0 insertions, 18 deletions
@@ -584,24 +584,6 @@ set confirm " set noesckeys -" By default, I prefer that figuring out where a region of text to fold away -" should be done by the indent level of its lines, since I tend to be careful -" about my indentation even in languages where it has no semantic meaning. -" -set foldmethod=indent - -" That said, I don't want any of these indent-based folds to start off closed. -" Therefore, we set the depth level at which folds should automatically start -" as closed to a rather high number, per the documentation's recommendations. -" -" I think of a Vim window with a file buffer loaded into it as -" a two-dimensional, planar view of the file, so that moving down one screen -" line means moving down one buffer line, at least when 'wrap' is unset. -" Folds break that mental model, and so I usually enable them explicitly only -" when I'm struggling to grasp some code with very long functions or loops. -" -set foldlevelstart=99 - " Automatic text wrapping options using flags in the 'formatoptions' option " begin here. I rely on the filetype plugins to set the 't' and 'c' flags for " this option to configure whether text or comments should be wrapped, as |