| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
I'm using the plugin_name.txt syntax suggested by the Vim documentation.
That may change in future as I study plugins written by experienced
authors like Tim Pope.
There will almost certainly be a lot more detail to add to each of
these.
|
|
|
|
| |
A brief explanation, an author name, and the license should do fine.
|
|
|
|
|
| |
I strongly suspect the presence of 'user_commands' implies it, but I'm
not sure.
|
|
|
|
|
|
| |
This prevents older versions of Vim like 6.2 from throwing "E1017:
Missing braces" on merely parsing this code, even though they don't
evaluate it.
|
|
|
|
|
|
|
|
| |
Renamed to flag_toggle.vim and placed in autoload using the namespaced
autoload function syntax.
I'm not sure this is the right approach yet, but I seem to pretty rarely
use a Vim earlier than 7.1 these days.
|
|
|
|
| |
Pretty useless, really.
|
| |
|
|
|
|
|
| |
We'll use this for defining Vim functions that should be dynamically
loaded when required, rather like how pathogen.vim does it.
|
|
|
|
|
|
|
|
|
| |
This is an experimental new plugin that provides a command to toggle
individual single-character flags in an option with a value of a set of
such flags, in my case 'formatoptions'.
A fair bit of evil eval()ing via :execute here, but I've tried to
control it with some strict patern matching.
|
|
|
|
|
| |
Calling this one copy_linebreak.vim. Renamed both the internal function
and the plugin key.
|
|
|
|
|
| |
Again using the <Plug> mapping abstraction and not defining the mapping
for the user.
|
|
|
|
|
|
| |
This properly abstracts out the StripTrailingWhitespace mapping rather
than forcing it to <leader>x within the plugin itself. A bit nicer this
way.
|
|
|
|
| |
The word "size" was added to this variable's name unnecesarily.
|
|
|
|
|
|
|
|
| |
Just for consistency with the other plugins I'm making.
I don't think I really like the cutesy names given to Vim plugins. I
prefer the slightly longer and maybe even namespaced names like Perl
distributions and modules have. Let's see how well this works.
|
| |
|
|
|
|
|
| |
Tentatively named command_typos.vim. I've just moved this as-is for now,
but it will need review, especially the hardcoded mappings.
|
|\
| |
| |
| |
| | |
* feature/rm-stray-vim:
Move misplaced command.vim file
|
|/
|
|
|
| |
Looks like this was added in a1ee04d for v0.4.0 and was intended to
replace the file in its correct path at vim/config/comment.vim.
|
|\
| |
| |
| |
| | |
* feature/review-ideas:
Remove an idea that has now been implemented
|
|/
|
|
|
| |
This was implemented and released in v0.4.0 as vim/plugin/bigfile.vim
and vim/doc/bigfile.txt.
|
|\
| |
| |
| |
| |
| | |
* release/v0.4.0:
Add vim/plugin to lint-vim arguments
Bump version number to 0.4.0
|
| |
| |
| |
| |
| |
| |
| | |
This ensures that new plugin code gets tested before being released.
We don't add the new vim/doc directory, as it's plain text rather than
VimL.
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* feature/vim-plugin:
Have bigfileturn local syntax off (configurably)
Make bigfile 'synmaxcol' setting configurable
Refactor plugin function for dependency injection
Rename variable and autocmd to use plugin prefix
Make bigfile size variable an option with default
Expand comment header for bigfile.vim
Move Vim big file options config into plugin
|
| | |
|
| |
| |
| |
| |
| | |
Defaults to 256 columns and only sets it if the option's value isn't
already lower than that.
|
| |
| |
| |
| |
| |
| |
| | |
Pass the filename to check and the size limit into the function directly
from the autocmd hook.
Improve commenting and spacing as we go.
|
| |
| |
| |
| |
| |
| | |
Just removing an underscore from the variable name so that
g:big_file_size becomes g:bigfile_size, and remove the "dotfiles" prefix
from the autocmd.
|
| |
| |
| |
| |
| | |
This arranges for g:big_file_size only to set itself to 10 MiB if the
variable is not already set, presumably by the user in their vimrc.
|
| |
| |
| |
| | |
Include some author and license metadata.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Created targets install-vim-doc and install-vim-plugin with accompanying
subdirectories of "vim".
Added a very short summary of what the plugin does to bigfile.txt.
I intend to spin off at least a couple of the blocks of my Vim
configuration that are starting to coalesce into distinct plugins unto
themselves, and will place the files in these directories.
|
| |\
| | |
| | |
| | |
| | |
| | | |
* hotfix/v0.3.2:
Always set GPG_TTY regardless of GPG_AGENT_INFO
Bump version number to 0.3.2
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* feature/options-audit:
Move 'tildeop' setting to new case.vim file
Move 'shellpipe' setting to more logical location
Make 'shellslash' setting conditional on feature
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Since it pertains to the casing of text, and there are potentially other
items that could go in here too.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It makes more sense next to 'shellslash' in vim/config/command.vim than
it does in vim/config/term.vim; the latter file is supposed to describe
settings related to the terminal, not the shell.
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
:help 'shellslash' says:
> 'shellslash' only works when a backslash can be used as a path
> separator. To test if this is so use:
> if exists('+shellslash')
This has actually already been done before in 795fd10, but the change
was lost in a merge with a branch that restructured the whole Vim
configuration.
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | | |
* hotfix/v0.3.2:
Always set GPG_TTY regardless of GPG_AGENT_INFO
Bump version number to 0.3.2
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
GnuPG 2.1 no longer sets the GPG_AGENT_INFO variable, making this a poor
choice of precondition for setting GPG_TTY:
<https://www.gnupg.org/faq/whats-new-in-2.1.html>
The manual page for gpg-agent(1) in GnuPG 2.1 says:
>You should always add the following lines to your .bashrc or whatever
>initialization file is used for all shell invocations:
>
> GPG_TTY=$(tty)
> export GPG_TTY
So we'll follow that literally, and just set it every time.
|
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | | |
* hotfix/v0.3.1:
Quote filename correctly in dfv(1df)
Bump version number to 0.3.1
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | | |
* hotfix/v0.3.1:
Quote filename correctly in dfv(1df)
Bump version number to 0.3.1
|
| | |
| | |
| | |
| | |
| | | |
If we don't do this, we run the risk of expanding an arbitrary macro
VERSION on any given system.
|
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* release/v0.3.0:
Bump version number to 0.3.0
Add dfv(1df) version-printing tool
Correct variable name in comment
Remove extraneous spacing between words
|
| |\ \ |
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | | |
* release/v0.3.0:
Bump version number to 0.3.0
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
* feature/version-dfv:
Add dfv(1df) version-printing tool
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is mostly just for fun, but could be handy later on when I'm
playing with distributed or automated deployments of tagged and verified
releases.
Like a few of the other shell scripts, this is built by abusing my
mi5(1df) wrapper to get static details baked into the shell script that
are only known at runtime.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
* feature/vim-syn-lint:
Correct variable name in comment
Remove extraneous spacing between words
|