| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This was introduced in commit 5d67a92. I'm surprised I haven't noticed
already. I would have thought this would cause glaring errors.
|
| |
|
|
|
|
|
| |
I'm thinking I might make this a generic mapping for "alternate
filetype".
|
|
|
|
|
|
| |
This was added as a Bash Readline macro in commit 25b513d, and has
proven to be very useful. I don't normally like insert mode maps in Vim,
especially Alt keys, so I'm not sure this will stick; we'll see.
|
|
|
|
|
| |
This prevents a jump to the first match, which I usually don't want, at
least immediately.
|
|
|
|
|
| |
May as well, now that we've dropped support for versions of Vim that
don't have it.
|
| |
|
|
|
|
|
| |
The relevant maps were removed in commit 5f1f5b9, but these unmap
instructions were left behind.
|
| |
|
| |
|
|
|
|
| |
This is a much nicer approach.
|
|
|
|
|
| |
Instead, remap \= specifically to use tidy(1) to reformat the whole
buffer.
|
|
|
|
|
| |
The mapping was removed in commit 44a75be, but not the autoloaded
function that the plugin was replacing.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
It's time!
The rest of the vimrc can probably be allowed to load, though.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
More overzealous undo-setting. I should wait until it becomes an actual
issue.
|
|
|
|
|
| |
It's not that these shouldn't be set, it's more that it's the wrong
place to do it, especially before they've caused any actual problems.
|
| |
|
|
|
|
|
| |
I never use these anyway; I'm firmly in the habit of using underscores
to represent the current line these days.
|
|
|
|
|
|
|
|
| |
I'm likely going to move away from Vim 6.0 support, at least for all of
this filetype stuff.
We will keep the one filetype load guard we actually need, which is the
HTML one, to stop plugins like markdown.vim from loading it.
|
|
|
|
|
| |
Allow the cpp plugin to load this, since it's the same anyway, and push
all the undo stuff together.
|
| |
|
| |
|
|
|
|
|
|
| |
These flags are also set and examined by the stock syntax for the "sh"
filetype, so checking for whether they're set at runtime for the
ftplugin just confuses things. Just clear them unconditionally instead.
|
|
|
|
|
|
|
| |
The function invoked to detect the HTML type for omnicompletion is
pretty big, sets a few buffer variables that it doesn't arrange to
clear, and I don't use it at all. Loading a dummy function in its place
seems to be better.
|
| |
|
|
|
|
| |
See commit 0748687.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Noticed that my b:undo_ftplugin script for this filetype was only
getting halfway through its work, and stopping at this command.
From `:help autocmd`:
> Note: The ":autocmd" command can only be followed by another command when the
> '|' appears before {cmd}. This works:
> :augroup mine | au! BufRead | augroup END
> But this sees "augroup" as part of the defined command:
> :augroup mine | au! BufRead * | augroup END
> :augroup mine | au BufRead * set tw=70 | augroup END
> Instead you can put the group name into the command:
> :au! mine BufRead *
> :au mine BufRead * set tw=70
> Or use :execute:
> :augroup mine | exe "au! BufRead *" | augroup END
> :augroup mine | exe "au BufRead * set tw=70" | augroup END
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 575f00d changed the setting for 'undodir' and similar path-based
settings to set the values conditionally based on the operating system
being used, while still setting them sensibly for "tiny" builds of Vim
on Unix, which skips all :if blocks.
This isn't necessary for 'undodir', because a tiny build of Vim won't
have the persistent_undo feature required for the option to exist at
all, so we can make this particular setting a little less awkward.
The 'backupdir' and 'directory' settings, however, need to keep their
existing structure to remain interoperable.
|
|
|
|
| |
This should probably be pushed upstream.
|
|
|
|
|
| |
Switching filetypes from "awk" to another type doesn't load the
indentation of the new type, due to the absence of this setting.
|
|
|
|
|
| |
These local buffer variable flags weren't being cleared correctly on a
filetype change.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This resolves the issue raised in f1b6f3b, where the mappings did not
work if the cursor was on the first line.
I had the colon `:` that starts the `ex` command and the `<C-U>` that
clears any existing command around the wrong way. Because CTRL-U in
normal mode scrolls up, it fails if we're already on the top line, and
the rest of the mapping looks to be skipped.
There don't seem to be any other instances of the same error that I can
find.
|
|
|
|
|
|
| |
I'm pretty tired of messing with all these. The defaults are fine, and
render nice and quickly; it's just too much of a hassle making it all
pixel-perfect, and the anti-aliasing is so often just rubbish.
|