aboutsummaryrefslogtreecommitdiff
path: root/vim/vimrc
Commit message (Collapse)AuthorAgeFilesLines
* Don't use VimL ==# for number comparisonsTom Ryder2017-11-061-1/+1
| | | | | | | | | | | The Google VimScript Guide says: <https://google.github.io/styleguide/vimscriptfull.xml#Portability> > Always use case-explicit operators for strings (=~# and =~?, never =~). > > This also applies to !~ == != > >= < and <= > This only applies for strings. == and >= are fine for numbers, but ==# > and >=# must be used for strings.
* Remove duplicated 'encoding' Vim configurationTom Ryder2017-10-311-5/+0
| | | | | This setting is already in vim/config/encoding.vim, having been copied there in 505a2c2; it was intended to be moved rather than copied.
* Remote `scriptencoding` definitionTom Ryder2017-10-301-2/+1
| | | | | | | There aren't actually any characters outside ASCII in any of the configuration, and for this to work they would need to have the `scriptencoding` at the head of that file, not at the top of the `.vimrc` as here, so I've just removed it.
* Remove 'nocompatible' settingTom Ryder2017-10-301-5/+0
| | | | | | | | | | | | | | | | | | vim-vint says: >Do not use nocompatible which has unexpected effects (see :help >nocompatible) I can't actually find anything in the help item it references that says that setting 'nocompatible' is bad, but the situation in which it's needed is very niche anyway; per the removed comment: >Don't make any effort to be compatible with vi, use more sensible >settings. This is only here in case this file gets loaded explicitly >with -u; the mere existence of a ~/.vimrc file already turns this off. We'll just leave it out, and see if anything bad happens..."if in doubt, rip it out".
* Use ==# consistently in Vim configTom Ryder2017-10-301-2/+2
| | | | | | | | | | | | I got a set of warnings from vim-vint about using just "==" for these comparisons: >Use robust operators `==#` or `==?` instead of `==` (see Google >VimScript Style Guide (Matching)) It does seem a lot more sensible to be explicit about case sensitivity, and not to lean on the configured 'ignorecase' value, especially if the user changes it.
* Test whether to load sahara colorschemeTom Ryder2017-10-291-1/+3
| | | | | | | | | | | | This is in preparation for config in vim/config/syntax.vim that will do a more comprehensive job of applying heuristics to figure out if the background is light or dark and hence what colours should be loaded for the appropriate scheme. The test for the GUI or 256 colours is repeated in the colorscheme code itself, but I think that's OK given that sahara.vim is distributed separately and others probably wouldn't use the kind of guards introduced in this commit.
* Add explanatory comment for Vim 'nocompatible'Tom Ryder2017-10-291-1/+3
|
* Load Vim Pathogen with :runtimeTom Ryder2017-10-291-0/+5
| | | | | | | | | | | | | | | | | | | | Per this suggestion from the `vim-pathogen` FAQ: <https://github.com/tpope/vim-pathogen#faq> >>Can I put pathogen.vim in a submodule like all my other plugins? > >Sure, stick it under `~/.vim/bundle`, and prepend the following to >your vimrc: > > runtime bundle/vim-pathogen/autoload/pathogen.vim This method avoids using symbolic links, which is desirable in general, and also removes the need for the `install-vim-pathogen` dependency of the `install-vim-plugin` target, since this is now done in Vim configuration. This also takes away another of the steps required for setting up the Vim configuration on Windows.
* Move 'nrformats' .vimrc config into subfileTom Ryder2017-10-281-4/+0
| | | | | | | This is an awkward filename and very unlikely to ever have anything but this one setting in it, but I can't think of any logical other place to put it. number.vim applies to line numbering, which is a distinct concept.
* Move line-joining .vimrc config into subfileTom Ryder2017-10-281-5/+0
|
* Move 'tildeop' .vimrc config into subfileTom Ryder2017-10-281-4/+0
| | | | | | This is an awkward filename and very unlikely to ever have anything but this one setting in it, but I can't think of any logical other place to put it.
* Move backspace .vimrc config into subfileTom Ryder2017-10-281-4/+0
|
* Move yanking .vimrc config into subfileTom Ryder2017-10-281-5/+0
|
* Move buffers .vimrc config into subfileTom Ryder2017-10-281-8/+0
|
* Move substitution .vimrc config into subfileTom Ryder2017-10-281-5/+0
|
* Move Fedora workaround .vimrc config into subfileTom Ryder2017-10-281-9/+0
|
* Move 'modeline' .vimrc setting to file.vim subfileTom Ryder2017-10-281-4/+0
|
* Move startup .vimrc config into subfileTom Ryder2017-10-281-4/+0
| | | | Just the 'shortmess' setting for now.
* Move syntax .vimrc config into subfileTom Ryder2017-10-281-12/+4
| | | | | | | | | Some refactoring is done here, because as noted in 5caa13c, my custom colorscheme is implemented as a plugin to be loaded by Pathogen, and hence isn't available into after it's done its work. I've removed the :set background line for now until I'm sure it's needed, because at the moment I'm not sure.
* Move completion .vimrc config into subfileTom Ryder2017-10-281-4/+0
| | | | | | Only one setting at the moment, but there's enough completion stuff even just in core Vim that I'm barely using, so this could be expanded upon later on.
* Move scrolling .vimrc config into subfileTom Ryder2017-10-281-6/+0
|
* Move visual-mode .vimrc config into subfileTom Ryder2017-10-281-6/+0
|
* Move 'shellslash' .vimrc conf into cmds subfileTom Ryder2017-10-281-4/+0
|
* Move file .vimrc config into subfileTom Ryder2017-10-281-28/+0
| | | | | Not completely sure this grouping is meaningful; I may refactor it a bit more later on.
* Add matching .vimrc config into subfilesTom Ryder2017-10-281-7/+0
| | | | | | "Matching" here refers to using % as a motion to the matching character or closing statement for a block, as enabled by Vim and enhanced by the optional matchit.vim included with the distribution.
* Move paste .vimrc config into subfileTom Ryder2017-10-281-7/+0
|
* Move wrapping .vimrc config into subfileTom Ryder2017-10-281-16/+0
|
* Move command .vimrc config into subfileTom Ryder2017-10-281-33/+0
| | | | | A little bit iffy on the grouping here, but it's still better than having it all lumped in the one file.
* Move line number .vimrc config into subfileTom Ryder2017-10-281-4/+0
| | | | | This file is rather short; it may turn out to make more sense to put these settings elsewhere a bit later.
* Move terminal .vimrc config into subfileTom Ryder2017-10-281-28/+0
|
* Move whitespace .vimrc config into subfileTom Ryder2017-10-281-15/+0
| | | | The StripTrailingWhitespace() function should perhaps be its own plugin.
* Move list .vimrc config into subfileTom Ryder2017-10-281-9/+0
| | | | | By "list" here I am referring to options for Vim's 'list' display setting, showing control characters visually.
* Move BigFileMeasures() .vimrc func into subfileTom Ryder2017-10-281-29/+0
| | | | | | Also add a note to IDEAS.md for later to consider packaging this as a proepr plugin, even if it doesn't actually leave the dotfiles repository just yet.
* Move format .vimrc config into subfileTom Ryder2017-10-281-32/+0
| | | | | The ToggleFormatFlag function might actually be better implemented as some sort of plugin.
* Move linebreak .vimrc config into subfileTom Ryder2017-10-281-32/+0
| | | | | | I'm not quite so sure about this one. The ToggleBreak() function might actually be better in a plugin on its own. The rest of it makes sense though.
* Move windows .vimrc config into subfileTom Ryder2017-10-281-28/+0
| | | | Not the operating system; Vim editor windows.
* Move wildmenu .vimrc config into subfileTom Ryder2017-10-281-24/+0
|
* Move spelling .vimrc config into subfileTom Ryder2017-10-281-27/+0
|
* Move indent .vimrc config into subfileTom Ryder2017-10-281-28/+2
|
* Move digraphs .vimrc config into subfileTom Ryder2017-10-281-7/+0
|
* Move syntax config back into .vimrcTom Ryder2017-10-281-0/+13
| | | | | | | | | | This reverts commit 5dba4c. The order of the configuration matters more for these settings, because the "sahara" colorscheme is only available after loading it as a plugin. I'll divest some other stuff that should be less sensitive to the order in which it's loaded first, and then tackle this one afterwards.
* Move syntax highlight .vimrc config into subfileTom Ryder2017-10-281-13/+0
| | | | | | This appears to break my choice of syntax colorscheme; the order of loading some of the previous directives in the configuration may have been relevant.
* Move search .vimrc config into subfileTom Ryder2017-10-281-27/+0
|
* Move swapfile .vimrc config into subfileTom Ryder2017-10-281-33/+0
|
* Add ! to runtime for sourcing vimrc subfilesTom Ryder2017-10-281-1/+1
| | | | | | | From :help :runtime: > When [!] is included, all found files are sourced. When it is not > included only the first found file is sourced.
* Move undo .vimrc config into subfileTom Ryder2017-10-281-33/+0
| | | | | Interestingly, this does not seem to work, and this configuration doesn't get loaded; I suspect the :runtime line is not quite right.
* Move backup .vimrc config into subfileTom Ryder2017-10-281-27/+0
| | | | Replace the test.vim file placed by 19f6f3 to do this.
* Set up .d-style vimrc subdir for config breakupTom Ryder2017-10-281-0/+4
| | | | | | | | | | | | Before loading up all the plugins proper from ~/.vim/bundle with Pathogen, apply :runtime to load all .vim files in a new config directory, installed by the Makefile. I hope that this will enable me to break most of my .vimrc up into logically-arranged subfiles. This is just a guess at a good way of doing this that will almost certainly need refinement and restructuring later.
* Move .vimrc 'encoding' to beneath scriptencodingTom Ryder2017-10-281-8/+6
| | | | | | | | | | | | | The Vim :help for "scriptencoding" specifies: > If you set the 'encoding' option in your .vimrc, > :scriptencoding must be placed after that. E.g.: > set encoding=utf-8 > scriptencoding utf-8 Also move it into the +multi_byte feature check, though this isn't too important as the :help specifies that the command is ignored if that feature is not available.
* Force silence for Vim syntax enablingTom Ryder2017-06-101-2/+2
| | | | | Might just be a peculiarity of OpenIndiana's build, but it raises an error as it tries to load nonexistent syntax files otherwise
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-28 13:31:02 +0000