| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
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
|
|\
| |
| |
| |
| | |
* release/v1.78.0:
Bump VERSION
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
| |
Only one line so far, but it's a good one: don't open a new window to
try to show me album art when I play FLACs, especially since it doesn't
work.
|
|
|
|
|
|
|
| |
From xset(1):
> The m option controls the mouse parameters; it may be abbreviated to
> 'm'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| |
| | |
* hotfix/v1.77.1:
Bump VERSION
Allow equal bounds in rndi(1df)
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Calling rndi(1df) like `rndi 1 1` should work; it should just always
yield one. Instead, it was complaining about the second bound not being
greater than the first.
I noticed this because I only had one background image in
~/.xbackgrounds and ran xrbg(1df), and it didn't know how to handle it.
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* release/v1.77.0:
Bump VERSION
Correct RHS of (un)important mail ftplugin map
Add an issue about mail filetypes in Vim
Remove a couple of unneeded XTerm resources
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
* hotfix/v1.76.2:
Correctly specify XTerm resources
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | | |
* release/v1.77.0:
Bump VERSION
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
| | | |
|
|\ \ \
| | |/
| |/|
| | |
| | | |
* hotfix/v1.76.2:
Correctly specify XTerm resources
|
| | | |
|
| |/
| |
| |
| |
| | |
I never would have guessed that "vt100" was what I was missing here...
but a closer reading of the xterm(1) manual page does show it.
|
| |\
| | |
| | |
| | |
| | |
| | | |
* hotfix/v1.76.1:
Rename xterm resources file to "XTerm"
Remove reference to X/Xresources.d/Xft
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | | |
* hotfix/v1.76.1:
Rename xterm resources file to "XTerm"
Remove reference to X/Xresources.d/Xft.
|
| | | |
|
| | | |
|
| |/
| |
| |
| | |
The file was removed in b456da1, but the reference to it was not.
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* release/v1.76.0:
Bump VERSION
Add color definitions to xterm resources
Correct TERM string for xterm
Remove some resources from URxvt
Add Dillo to README.md configuration list
Add single quotes to description of Vim options
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
* hotfix/v1.75.1:
Rebuild dotfiles(7df) manual
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | | |
* release/v1.76.0:
Bump VERSION
|
|/ / / |
|
| | | |
|