| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| | |
* hotfix/v0.26.2:
Bump version number to 0.26.2
Actually remove pathogen bundle dir
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
* hotfix/v0.26.1:
Bump version number to 0.26.1 (hotfix)
Exclude root-level files from Vim bundles
Restore install-vim-autoload target
|
| | |
|
| |
| |
| |
| |
| |
| | |
Create the plugin directory hierarchy first, and then copy the files in
as long as they're at least one file deep. This prevents files like
README.markdown landing in ~/.vim.
|
|/
|
|
| |
It was mistakenly removed in 3e2740f for v0.26.0.
|
|\
| |
| |
| |
| |
| | |
* release/v0.26.0:
Bump version number to 0.26.0
Remove Pathogen from Vim setup
|
| | |
|
| |\
| | |
| | |
| | |
| | | |
* feature/no-pathogen:
Remove Pathogen from Vim setup
|
| |/
| |
| |
| |
| |
| |
| | |
Given that all of this is installed rather than symbolically linked,
there's not really any harm following the old mixed ~/.vim layout for
plugins. It's one less dependency and it makes the setup quite a bit
less complicated.
|
| |\
| | |
| | |
| | |
| | | |
* release/v0.25.0:
Bump version number to 0.25.0
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* release/v0.25.0:
Bump version number to 0.25.0
Suspend 'C' from 'cpoptions' for sh syn extensions
Join short-circuit line in detect_background.vim
Break some continued lines in Vim indent files
Remove 'mac' from 'fileformats'
Tweak 'cpoptions' C flag instead of 'nocompatible'
Remove a baseless assertion I made in a config
Make entire syntax config dependent on load state
Activate syntax settings conditionally
|
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* feature/vimrc-review:
Suspend 'C' from 'cpoptions' for sh syn extensions
Join short-circuit line in detect_background.vim
Break some continued lines in Vim indent files
Remove 'mac' from 'fileformats'
Tweak 'cpoptions' C flag instead of 'nocompatible'
Remove a baseless assertion I made in a config
Make entire syntax config dependent on load state
Activate syntax settings conditionally
|
| | |
| | |
| | |
| | | |
This allows me to use line-breaking to keep the file readable.
|
| | |
| | |
| | |
| | |
| | | |
This makes the block work correctly when 'compatible' is set and 'C' is
in 'cpoptions'.
|
| | |
| | |
| | |
| | |
| | | |
This will mean they load correctly when the 'C' flag preventing
line-breaking is in 'cpoptions', and 'compatible' is set.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It seems unlikely that I'll ever edit a MacOS encoded file in my
lifetime on the Unix and Windows systems to which these dotfiles are
deployed, and when 'compatible' is set, the default empty value for this
option breaks everything with a bunch of ^J characters in every
god-fearing file. Not worth the trouble.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In order for the configuration to be successfully loaded, the only
option in the vi 'cpoptions' settings for 'compatible' is "C". From
:help 'cpoptions':
> C Do not concatenate sourced lines that start with a backslash.
> See line-continuation.
With this flag removed from 'cpoptions' if 'compatible' does happen to
be set, the configuration parses just fine, and then we can put it back
at the end if we need to.
This is a less aggressive approach than just turning off 'compatible'
entirely if it happens to be set, whether because the user wanted it
that way before loading the configuration or because Vim was started as
ex(1).
My plugins and ftplugins are all conditional on 'compatible' not being
set, anyway.
|
| | |
| | |
| | |
| | |
| | | |
Don't claim that syntax files tend to assume 'autoindent' is set, as it
doesn't seem to be true.
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Per an oft-made recommendation on /r/vim .vimrc review threads:
<https://www.reddit.com/r/vim/comments/6znskl/vimrc_review_thread/dnbmvxv/>
> Re-sourcing the vimrc won't clobber any of your personal highlight
> settings and the if part helps avoid unneeded re-execution/reprocessing.
|
| |\
| | |
| | |
| | |
| | | |
* release/v0.24.0:
Bump version number to 0.24.0
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
* release/v0.24.0:
Bump version number to 0.24.0
Always add --log to `git merge`
Refactor directory creation in plugins
Remove HTML and PHP syntax highlighting tweaks
Clear unwanted syntax group, don't link to NONE
|
| |/ |
|
| |\
| | |
| | |
| | |
| | | |
* feature/vim-plugin:
Refactor directory creation in plugins
|
| | |
| | |
| | |
| | | |
No functional changes here, just removing a little duplicate code.
|
| |\ \
| | |/
| |/|
| | |
| | | |
* feature/git-merge:
Always add --log to `git merge`
|
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | | |
* feature/vim-after-syntax:
Remove HTML and PHP syntax highlighting tweaks
Clear unwanted syntax group, don't link to NONE
|
| | |
| | |
| | |
| | |
| | | |
The things they were intended to fix aren't actually that bad, on
review.
|
| |/ |
|
| |\
| | |
| | |
| | |
| | | |
* release/v0.23.0:
Bump version number to 0.23.0
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* release/v0.23.0:
Bump version number to 0.23.0
Remove unused `self` var from clog(1df)
Change double-quote printf pattern to single-quote
Move ShellCheck line to correct place in sra(1df)
Quote EDITOR/VISUAL assignments for clarity
Explicitly ignore uninteresting tree(1) opts
Refactor clog(1df), allow args and non-term stdin
Reimplement bl(1df) in Awk
Separate ax(1df) manpage args from command
Make newline explicit for ax(1df)
Make first ax(1df) arg safer, warn on second arg
Correct monospaced blocks in Vim plugin docs
|
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* feature/shellcheck-0.4.7-review:
Remove unused `self` var from clog(1df)
Change double-quote printf pattern to single-quote
Move ShellCheck line to correct place in sra(1df)
Quote EDITOR/VISUAL assignments for clarity
Explicitly ignore uninteresting tree(1) opts
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ShellCheck:
In bin/clog.sh line 2:
self=clog
^-- SC2034: self appears unused. Verify it or export it.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ShellCheck 0.4.7 pointed to this indirectly:
In bin/sshi line 24:
printf "%s:%u -> %s:%u (%s)\n" \
^-- SC1117: Backslash is literal in "\n". Prefer explicit escaping: "\\n".
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ShellCheck 0.4.7 was upset about this:
In bin/sra line 7:
ssh -qt -- "$hostname" "$@" <&3 # shellcheck disable=SC2029
^-- SC1073: Couldn't parse this simple command.
^-- SC1126: Place shellcheck directives before commands, not after.
^-- SC1072: Fix any mentioned problems and try again.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This appeases ShellCheck 0.4.7, which is fretting that I meant a command
expansion. I didn't, but it seems a bit nicer to quote these anyway.
In sh/profile.d/editor.sh line 4:
EDITOR=ed
^-- SC2209: Use var=$(command) to assign output (or quote to assign string).
In sh/profile.d/editor.sh line 22:
EDITOR=ex
^-- SC2209: Use var=$(command) to assign output (or quote to assign string).
In sh/profile.d/visual.sh line 2:
VISUAL=vi
^-- SC2209: Use var=$(command) to assign output (or quote to assign string).
|
| |/
| |
| |
| |
| |
| |
| |
| | |
ShellCheck 0.4.7 complained about this:
In sh/shrc.d/tree.sh line 12:
case $opt in
^-- SC2220: Invalid flags are not handled. Add a *) case.
|
| |\
| | |
| | |
| | |
| | |
| | | |
* feature/bin-review:
Refactor clog(1df), allow args and non-term stdin
Reimplement bl(1df) in Awk
|
| | |
| | |
| | |
| | |
| | | |
This makes a bit clearer how awkward the rlwrap(1) code is, too. It may
not be worth keeping it.
|
| |/
| |
| |
| | |
This is shorter and tidier.
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
* feature/ax-safety:
Separate ax(1df) manpage args from command
Make newline explicit for ax(1df)
Make first ax(1df) arg safer, warn on second arg
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Just for a clearer visual distinction. This probably needs to be done
for other manual pages, too.
We use zero-width characters (\&) at the start of the lines beginning
with apostrophes so that they get printed literally.
|
| | |
| | |
| | |
| | |
| | | |
This makes it a little more flexible, if you genuinely don't want a
newline in the output.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The format in the first argument does not need to be evaluated, so it
can be passed in a simple awk variable.
The second argument is evaluated, by design, so code injection is
trivial. It's probably a good idea to warn users about this explicitly.
$ ax '0);system("cat /etc/passwd")'
Make the whole thing a little terser, too, with the awk program
construction, variable assignment, and invocation all on one line.
|
| |\
| | |
| | |
| | |
| | | |
* feature/vim-doc-fix:
Correct monospaced blocks in Vim plugin docs
|