| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tiny builds of Vim that exclude the eval feature throw errors at the
:let commands in this file:
$ vim.tiny
Error detected while processing /home/tom/.vim/config/netrw.vim:
line 2:
E319: Sorry, the command is not available in this version: let g:netrw_banner = 0
line 5:
E319: Sorry, the command is not available in this version: let g:netrw_silent = 1
line 8:
E319: Sorry, the command is not available in this version: let g:netrw_liststyle = 3
line 11:
E319: Sorry, the command is not available in this version: let g:netrw_list_hide = '^\.$,^tags$'
Press ENTER or type command to continue
This code was not being run on such builds before commit 538b71c,
because it was in an "after" directory for the netrw plugin and would
have been skipped.
Wrapping a check for has('eval') around this whole file fixes the
problem. netrw.vim won't run without this feature anyway.
|
| |
|
|\
| |
| |
| |
| |
| | |
* hotfix/v0.4.1:
Don't show search option state on mode changes
Bump version number to 0.4.1
|
| |
| |
| |
| |
| |
| |
| | |
Commit 92f2c78 added these suffixes to the option settings to show the
value of the option after it had been set, but this isn't actually
appropriate for the autocmd here; it means the value of 'hlsearch' is
echoed every time insert mode is entered or left.
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* release/v0.4.0:
Add vim/plugin to lint-vim arguments
Bump version number to 0.4.0
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
Move 'tildeop' setting to new case.vim file
Move 'shellpipe' setting to more logical location
Make 'shellslash' setting conditional on feature
|
| |
| |
| |
| |
| |
| |
| | |
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
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was unintentionally committed in e36efd4. The correct name of the
variable is b:is_ksh. b:is_kornshell_proper was a rejected first
revision of the name.
|
| | |/
| | |
| | |
| | | |
No functional effect.
|
| | |\
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | | |
I'm going to pretend this is a crucially important production fix, in
order to try out the "hotfix" part of the "Git flow" workflow.
|
|/ / |
|
|\ \ |
|
|\ \ \ |
|
| | | |\
| | | |/
| | |/| |
|
| | |/ |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | | |
Just for consistency.
|
| | | |
| | | |
| | | |
| | | | |
Just for future reference, but the work for this branch is done now.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This makes them more consistent with the work already done on the check
and lint scripts for the other targets.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use a positive list of things to check rather than just excluding
`bundle`; it's a little clearer what it's doing that way, and easier to
add paths to check rather than paths to exclude.
We also correctly leverage `vint` accepting multiple arguments, like
`shellcheck`.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There's no point making a list out of just one globbed item; we'll just
inline it. That's also done for some of the other `check` scripts
anyway.
|