| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
That is, apply <buffer> and <silent> to each of them, to make them only
apply to the current buffer and to prevent them from echoing the command
they're running.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This is a much better method of calling external programs on the
buffer's contents, not just because it avoids the mess of :execute
evaluation but also because it doesn't require that there actually be a
filename for the current buffer.
This drastically simplifies the HTML tidy(1) call in particular.
|
| |
|
|
| |
We should probably avoid this sort of abbreviation in scripts.
|
| |
|
|
|
| |
It doesn't seem to be in very old Vims; worth testing for to avoid
errors if I try to use the function.
|
| |
|
|
|
|
|
| |
From ":help <LocalLeader>":
> In a global plugin <Leader> should be used and in a filetype plugin
> <LocalLeader>. "mapleader" and "maplocalleader" can be equal.
|
| |
|
|
|
|
| |
I'm still getting used to the structure of the configuration here, and
had mistakenly put these indent-related settings into files in the
ftplugin directory.
|
| |
|
|
|
|
|
|
|
|
| |
For some languages in which I write often: C, HTML, Perl, PHP, and
shell scripts.
All of these values presently match the defaults specified in
config/indent.vim, but for languages I commonly use it's probably
appropriate to have files to set the indent settings explicitly anyway,
especially if we switched from a filetype with different values.
|
|
|
None of the settings in here need to be run after the core configuration
files are loaded, so I'll put them in a slightly more accessible or
logical place.
This adds a new target `install-vim-ftplugin`, and makes that a
prerequisite of the `install-vim` target.
|
