| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Might just be a peculiarity of OpenIndiana's build, but it raises an
error as it tries to load nonexistent syntax files otherwise
|
|
|
|
| |
These have fallen into disuse--`set ft=...` seems to be fine
|
|
|
|
|
| |
It impedes accurate copypasting from terminal emulators otherwise, which
is the main reason I implemented \b
|
| |
|
|
|
|
| |
Feels weird to come back to it; let's see if I decide to stay
|
|
|
|
| |
<https://i.imgur.com/ze2uZQG.png>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Found in @tpope's vim-sensible
|
|
|
|
|
| |
Ex mode is actually kind of handy when doing a set of text
transformations, e.g. substitutions/pattern deletions
|
|
|
|
|
| |
Doing a lot more shell and some C programming these days and this has
actually become sort of useful.
|
|
|
|
|
| |
I unmapped this initially because I was using the Escape key; nowadays I
never do, I use Ctrl+[, so it's no longer doing any harm
|
|
|
|
| |
Using ~/.vim/after instead
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
At least on Debian's stock Vim on really old machines, loading Pathogen
causes a segfault that leaves Vim looping forever.
|
| |
|
| |
|