| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Handle both kinds of templated temporary files produced by sudoedit(8):
* /var/tmp/foo.XXXXXXXX
* /var/tmp/fooXXXXXXXX.bar
This means that editing /etc/resolv.conf now highlights correctly,
having also in this commit moved the sudo detection to *before* the
.conf fallback.
The hardcoded temporary path for finding the files probably needs to be
either determined at runtime or made configurable by the user.
|
| |
|
| |
|
|
|
|
|
|
| |
Commit 35ba8df removed this, but the bell still rings on a TTY and in
an X terminal outside of tmux. I didn't notice because the machine I was
using doesn't have a PC speaker.
|
|
|
|
|
| |
This includes the creation of a hitherto-unneeded Makefile target
install-vim-syntax.
|
| |
|
|
|
|
|
|
|
|
|
| |
Error message is:
Error detected while processing /home/tom/.vim/after/syntax/sh.vim:
line 10:
E108: No such variable: "g:is_kornshell"
Press ENTER or type command to continue
|
|
|
|
|
|
|
| |
This reverts commit dce5abc0724428f805562dd32bf9a71677d55aaa.
On review, paste_open is good enough. I can always dig this back up
again if I need to.
|
|
|
|
| |
Still a little experimental; no documentation (or distribution) yet.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It's overkill; just add comments explaining why we're setting what the
Vim default is.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This would be great if it was immediate and didn't require the
CursorMoved event, but as it stands it's not really an improvement over
just my \w mapping to toggle 'wrap'.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This should be a command, and may very well be useful outside of mail
contexts, but this will do OK for now.
|
|
|
|
|
|
| |
If we don't actually want to know whether the string occurs *anywhere*
in the line, just at the start, we should really use substring
operations or plain old regular expression tests.
|
| |
|
| |
|
|
|
|
|
| |
This is just to prevent the `:call search(...)` command from showing up
in the command line when the map is invoked.
|
| |
|
|
|
|
| |
This preserves the user's primary search pattern.
|