aboutsummaryrefslogtreecommitdiff
path: root/vim/vimrc
Commit message (Collapse)AuthorAgeFilesLines
* Use uppercase letters in <C-A>, <C-B> consistentlyTom Ryder2018-06-101-2/+2
|
* Set some more 'listchars' optionsTom Ryder2018-06-071-3/+5
|
* Replace mail_mutt.vim with mim(1df)Tom Ryder2018-06-071-7/+0
| | | | Way better, and more generally useful.
* Remove vestigial comment from .vimrcTom Ryder2018-06-061-6/+0
|
* Remove duplicate 'encoding' settingTom Ryder2018-06-061-5/+0
|
* Remove 'backupskip' settingTom Ryder2018-06-061-4/+0
|
* Inline some option flag commentsTom Ryder2018-06-061-32/+16
|
* Add a little more syntax contextTom Ryder2018-06-061-2/+2
|
* Move syntax block upTom Ryder2018-06-061-18/+18
|
* Factor out password redaction into new pluginTom Ryder2018-06-061-43/+0
|
* Spacing adjustmentsTom Ryder2018-06-061-4/+0
|
* Abbreviate and invert j/gj,k/gk mappingsTom Ryder2018-06-061-4/+4
|
* Refactor vim/vimrcTom Ryder2018-06-061-172/+127
| | | | | Rearranging order where logical, adjust comments, remove line continuation guard and just join all relevant lines.
* Consolidate .vimrc and .vim/filetype.vimTom Ryder2018-06-061-1/+565
| | | | And add .vim/script.vim, to be composed in the next commit
* Remove Pathogen from Vim setupTom Ryder2018-01-231-21/+1
| | | | | | | Given that all of this is installed rather than symbolically linked, there's not really any harm following the old mixed ~/.vim layout for plugins. It's one less dependency and it makes the setup quite a bit less complicated.
* Tweak 'cpoptions' C flag instead of 'nocompatible'Tom Ryder2018-01-211-2/+14
| | | | | | | | | | | | | | | | | | | | | In order for the configuration to be successfully loaded, the only option in the vi 'cpoptions' settings for 'compatible' is "C". From :help 'cpoptions': > C Do not concatenate sourced lines that start with a backslash. > See line-continuation. With this flag removed from 'cpoptions' if 'compatible' does happen to be set, the configuration parses just fine, and then we can put it back at the end if we need to. This is a less aggressive approach than just turning off 'compatible' entirely if it happens to be set, whether because the user wanted it that way before loading the configuration or because Vim was started as ex(1). My plugins and ftplugins are all conditional on 'compatible' not being set, anyway.
* Restore 'nocompatible' set to vimrcTom Ryder2017-11-231-0/+3
| | | | | | Otherwise, the line-continuation in the ~/.vimrc fails if compatibility mode survives the invocation step, for example if the vimrc file is sourced directly with the -u option, or if vim is invoked as "ex".
* Move mapleader settings before .vimrc conf sourceTom Ryder2017-11-141-0/+6
| | | | | | | | | | From :help mapleader: > Note that the value of "mapleader" is used at the moment the mapping > is defined. Changing "mapleader" after that has no effect for already > defined mappings. So the order of evaluation matters.
* 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-16 12:15:47 +0000