| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 70fcb35 incorrectly built the dotfiles(7) manual without the
header required by the Pandoc converter. Rebuilt it properly by making a
script in a new directory "dist" which is to be run by the maintainer
whenever its source file README.md is updated. This should probably be
automated on my end with Git hooks.
The reason we don't include the Pandoc recipe for making this manual as
a target in the Makefile is to do with the heavy dependency of Pandoc,
for which packages are not available on some desirable operating
systems, as arranged in a8ab2cf.
Also added the new install-man target as one of the default subtargets
of `install`.
|
| |
|
|
|
|
| |
Mostly to reflect its split into subfiles in ~/.vim/config.
|
|\
| |
| |
| |
| | |
This development branch split .vimrc into many logically-grouped
subfiles in ~/.vim/config/*.vim.
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Just the 'shortmess' setting for now.
|
| |
| |
| |
| |
| |
| | |
Per 6ca11a5, I've confirmed I do still need this, otherwise the default
colorschemes (not sahara.vim) assume a bright background and show very
dark colours.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Not completely sure this grouping is meaningful; I may refactor it a bit
more later on.
|
| |
| |
| |
| |
| |
| | |
"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.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
A little bit iffy on the grouping here, but it's still better than
having it all lumped in the one file.
|
| |
| |
| |
| |
| | |
This file is rather short; it may turn out to make more sense to put
these settings elsewhere a bit later.
|
| | |
|
| |
| |
| |
| | |
The StripTrailingWhitespace() function should perhaps be its own plugin.
|
| |
| |
| |
| |
| | |
By "list" here I am referring to options for Vim's 'list' display
setting, showing control characters visually.
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
The ToggleFormatFlag function might actually be better implemented as
some sort of plugin.
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
Not the operating system; Vim editor windows.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
From :help :runtime:
> When [!] is included, all found files are sourced. When it is not
> included only the first found file is sourced.
|
| |
| |
| |
| |
| | |
Interestingly, this does not seem to work, and this configuration
doesn't get loaded; I suspect the :runtime line is not quite right.
|
| |
| |
| |
| | |
Replace the test.vim file placed by 19f6f3 to do this.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
|
|
|
| |
From :help 'shellslash':
> 'shellslash' only works when a backslash can be used as a path
> separator. To test if this is so use:
> if exists('+shellslash')
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| | |
No differences.
|
| |\
| |/
|/| |
|
|\ \
| | |
| | |
| | | |
No differences.
|