aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'release/v0.4.0'v0.4.0Tom Ryder2017-11-0210-34/+128
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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
| * Add vim/plugin to lint-vim argumentsTom Ryder2017-11-021-0/+1
| | | | | | | | | | | | | | 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.
| * Bump version number to 0.4.0Tom Ryder2017-11-021-2/+2
| |
| * Merge branch 'feature/vim-plugin' into developTom Ryder2017-11-024-29/+83
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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
| | * Have bigfileturn local syntax off (configurably)Tom Ryder2017-11-021-0/+10
| | |
| | * Make bigfile 'synmaxcol' setting configurableTom Ryder2017-11-021-2/+7
| | | | | | | | | | | | | | | Defaults to 256 columns and only sets it if the option's value isn't already lower than that.
| | * Refactor plugin function for dependency injectionTom Ryder2017-11-021-13/+21
| | | | | | | | | | | | | | | | | | | | | Pass the filename to check and the size limit into the function directly from the autocmd hook. Improve commenting and spacing as we go.
| | * Rename variable and autocmd to use plugin prefixTom Ryder2017-11-021-4/+4
| | | | | | | | | | | | | | | | | | 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.
| | * Make bigfile size variable an option with defaultTom Ryder2017-11-021-2/+4
| | | | | | | | | | | | | | | 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.
| | * Expand comment header for bigfile.vimTom Ryder2017-11-021-1/+8
| | | | | | | | | | | | Include some author and license metadata.
| | * Move Vim big file options config into pluginTom Ryder2017-11-023-1/+23
| |/ |/| | | | | | | | | | | | | | | | | | | 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.
* | Merge branch 'hotfix/v0.3.2'v0.3.2Tom Ryder2017-11-012-4/+3
|\ \ | | | | | | | | | | | | | | | * hotfix/v0.3.2: Always set GPG_TTY regardless of GPG_AGENT_INFO Bump version number to 0.3.2
| | * Merge branch 'feature/options-audit' into developTom Ryder2017-11-024-3/+42
| | |\ | | | | | | | | | | | | | | | | | | | | | | | | * feature/options-audit: Move 'tildeop' setting to new case.vim file Move 'shellpipe' setting to more logical location Make 'shellslash' setting conditional on feature
| | | * Move 'tildeop' setting to new case.vim fileTom Ryder2017-11-011-0/+0
| | | | | | | | | | | | | | | | | | | | Since it pertains to the casing of text, and there are potentially other items that could go in here too.
| | | * Move 'shellpipe' setting to more logical locationTom Ryder2017-11-012-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| | | * Make 'shellslash' setting conditional on featureTom Ryder2017-11-011-0/+39
| | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | :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.
| | * Merge branch 'hotfix/v0.3.2' into developTom Ryder2017-11-012-4/+3
| | |\ | | |/ | |/| | | | | | | | | | * hotfix/v0.3.2: Always set GPG_TTY regardless of GPG_AGENT_INFO Bump version number to 0.3.2
| * | Always set GPG_TTY regardless of GPG_AGENT_INFOTom Ryder2017-11-011-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | Bump version number to 0.3.2Tom Ryder2017-11-011-2/+2
|/ /
* | Merge branch 'hotfix/v0.3.1'v0.3.1Tom Ryder2017-11-012-3/+3
|\ \ | | | | | | | | | | | | | | | * hotfix/v0.3.1: Quote filename correctly in dfv(1df) Bump version number to 0.3.1
| | * Merge branch 'hotfix/v0.3.1' into developTom Ryder2017-11-012-3/+3
| | |\ | | |/ | |/| | | | | | | | | | * hotfix/v0.3.1: Quote filename correctly in dfv(1df) Bump version number to 0.3.1
| * | Quote filename correctly in dfv(1df)Tom Ryder2017-11-011-1/+1
| | | | | | | | | | | | | | | If we don't do this, we run the risk of expanding an arbitrary macro VERSION on any given system.
| * | Bump version number to 0.3.1Tom Ryder2017-11-011-2/+2
|/ /
* | Merge branch 'release/v0.3.0'v0.3.0Tom Ryder2017-11-017-6/+32
|\ \ | | | | | | | | | | | | | | | | | | | | | * 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
* \ \ Merge branch 'hotfix/v0.2.1'v0.2.1Tom Ryder2017-10-315-8/+8
|\ \ \
| | | * Merge branch 'release/v0.3.0' into developTom Ryder2017-11-011-2/+2
| | | |\ | | | |/ | | |/| | | | | | | | | * release/v0.3.0: Bump version number to 0.3.0
| | * | Bump version number to 0.3.0Tom Ryder2017-11-011-2/+2
| | |/
| | * Merge branch 'feature/version-dfv' into developTom Ryder2017-11-014-0/+27
| | |\ | | | | | | | | | | | | | | | | * feature/version-dfv: Add dfv(1df) version-printing tool
| | | * Add dfv(1df) version-printing toolTom Ryder2017-11-014-0/+27
| | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * Merge branch 'feature/vim-syn-lint' into developTom Ryder2017-11-012-4/+3
| | |\ | | | | | | | | | | | | | | | | | | | | * feature/vim-syn-lint: Correct variable name in comment Remove extraneous spacing between words
| | | * Correct variable name in commentTom Ryder2017-11-011-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| | | * Remove extraneous spacing between wordsTom Ryder2017-11-011-1/+1
| | |/ | | | | | | | | | No functional effect.
| | * Merge branch 'hotfix/v0.2.1' into developTom Ryder2017-10-315-8/+8
| | |\ | | |/ | |/|
| * | Use "shell" not "sh" consistentlyTom Ryder2017-10-314-6/+6
| | | | | | | | | | | | | | | 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.
| * | Bump version number to 0.2.1Tom Ryder2017-10-311-2/+2
|/ /
* | Merge branch 'release/v0.2.0'v0.2.0Tom Ryder2017-10-3120-55/+138
|\ \
* \ \ Merge branch 'release/v0.1.0'v0.1.0Tom Ryder2017-10-312-1/+3
|\ \ \
| | | * Merge branch 'release/v0.2.0' into developTom Ryder2017-10-311-2/+2
| | | |\ | | | |/ | | |/|
| | * | Bump version number to 0.2.0Tom Ryder2017-10-311-2/+2
| | |/
| | * Merge branch 'feature/lint-stable' into developTom Ryder2017-10-3119-53/+136
| | |\
| | | * Correct some vestigial programs to shell namesTom Ryder2017-10-313-3/+3
| | | | | | | | | | | | | | | | Just for consistency.
| | | * Add idea and issue regarding checking and lintingTom Ryder2017-10-312-0/+5
| | | | | | | | | | | | | | | | Just for future reference, but the work for this branch is done now.
| | | * Bring Xinit check/lint scripts up to standardTom Ryder2017-10-312-4/+11
| | | | | | | | | | | | | | | | | | | | This makes them more consistent with the work already done on the check and lint scripts for the other targets.
| | | * Revamp `lint-vim` target for consistencyTom Ryder2017-10-311-5/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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`.
| | | * Inline check arguments for URxvt perlsTom Ryder2017-10-311-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| | | * Check and lint URxvt Perls correctlyTom Ryder2017-10-313-5/+11
| | | | | | | | | | | | | | | | | | | | | | | | Require that the URxvt Perls are built correctly. There's only one at the moment, so I'll make that the single prerequisite for the `check-urxvt` target.
| | | * Add option terminators to some stray `set` callsTom Ryder2017-10-312-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding the option terminator "--" directly after the `set` call ensures that all following arguments will be interpreted as new arguments for the list. This is probably not strictly applicable here, because the paths that will be stacked up don't start with dashes by definition, but it's likely good practice.
| | | * Apply revisions to `check-zsh` target as wellTom Ryder2017-10-311-4/+8
| | | | | | | | | | | | | | | | I forgot about this one.
| | | * Tidy and correct linting for all three shellsTom Ryder2017-10-316-28/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reduce each one to target only the dotfiles specifically for that shell, as opposed to previously where for example the `check-sh` target was checking shell shims in for `mpd` and `plenv`. I'm still not completely sure that's the right approach, but it's at least less conceptually muddy than what we had before. Notably, the check and lint for Korn shell includes a single POSIX shell script file in its `shrc.d` subdirectory, so that check is executed separately.
| | | * Use shell name not command in check/lint messagesTom Ryder2017-10-312-6/+6
| | | | | | | | | | | | | | | | This is a little bit clearer and nicer to read, I think.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-20 02:06:52 +0000