| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* release/v0.10.0:
Bump version number to 0.10.0
Correct a comment
Use stridx() instead of very-nomagic regex match
Use strlen() instead of len()
Escape option value assign correctly
Extend toggle_option_flag.vim for string flags
Rename l:op to l:operation for clarity
Separate command building from execution in toggle
Use idiomatic VimL regex for param validation
Restore some judicious \m\C hedging in Vim
Remove redundant has('eval') VimL test
Caution about :execute not eval() in VimL comments
Move pipes from end to start of continued lines
Remove \m\C prefix from inapplicable VimL regexes
Don't use VimL ==# for number comparisons
Don't overwrite plugin-specified user commands
Make background detection return not set value
Complete ToggleOptionFlag commands with opt names
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | | |
* feature/vim-stridx:
Correct a comment
Use stridx() instead of very-nomagic regex match
|
| | |
| | |
| | |
| | | |
This likely got butchered by a wayward search-and-replace.
|
| |/
| |
| |
| |
| | |
I couldn't find this function at first, but it's what I need: a way to
check whether a string appears in another one.
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* feature/vim-plug-review:
Use strlen() instead of len()
Escape option value assign correctly
Extend toggle_option_flag.vim for string flags
Rename l:op to l:operation for clarity
Separate command building from execution in toggle
Use idiomatic VimL regex for param validation
Restore some judicious \m\C hedging in Vim
Remove redundant has('eval') VimL test
Caution about :execute not eval() in VimL comments
Move pipes from end to start of continued lines
Remove \m\C prefix from inapplicable VimL regexes
Don't use VimL ==# for number comparisons
Don't overwrite plugin-specified user commands
Make background detection return not set value
Complete ToggleOptionFlag commands with opt names
|
| | |
| | |
| | |
| | |
| | |
| | | |
strlen() is older, and also more specific to what we want to do. len()
just happens to work on strings, but was introduced for counting Lists
and Dictionaries.
|
| | |
| | |
| | |
| | | |
This allows e.g.: ':ToggleOptionFlag fillchars diff: '; note the whitespace!
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit extends toggle_option_flag.vim to allow the exported
commands to toggle values of more than one character, for
comma-separated options like 'switchbuf', e.g.:
:ToggleOptionFlag switchbuf useopen
|
| | |
| | |
| | |
| | | |
Just to avoid confusing it with something like l:option.
|
| | |
| | |
| | |
| | |
| | | |
These are functionally equivalent; it's just clearer and more
editing-friendly to do one thing at a time.
|
| | |
| | |
| | |
| | | |
\a and \L are, I think, perlre-style VimL regex inventions.
|
| | |
| | |
| | |
| | |
| | | |
These are technically not really needed, but this is more consistent
with good style recommendations in the Google VimScript style guide.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
From what I understand from ":help if", ancient Vim and/or vim-tiny
without the 'eval' feature will simply gloss over all commands between
:if and :endif without executing them. Therefore as soon as we test a
version, we're implicitly excluding everything that doesn't have 'eval'
anyway.
|
| | |
| | |
| | |
| | | |
May as well refer to the actual command I'm using.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Google Vimscript Guide says:
<https://google.github.io/styleguide/vimscriptfull.xml#Whitespace>
> Place one space after the backslash denoting a line continuation.
>
> When continuing a multi-line command a pipe can be substituted for
> this space as necessary, as follows:
>
> autocommand BufEnter <buffer>
> \ if !empty(s:var)
> \| call some#function()
> \|else
> \| call some#function(s:var)
> \|endif
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Google VimScript Guide says:
<https://google.github.io/styleguide/vimscriptfull.xml#Portability>
> Always use case-explicit operators for strings (=~# and =~?, never =~).
>
> This also applies to !~ == != > >= < and <=
> This only applies for strings. == and >= are fine for numbers, but ==#
> and >=# must be used for strings.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The Google Vimscript Style Guide says:
<https://google.github.io/styleguide/vimscriptguide.xml#Commands>
> Excluding [!] prevents your plugin from silently clobbering existing
> commands. Command conflicts should be resolved by the user.
This makes sense to me as we can think of <Plug> mapping and user
commands as being the user-accessible portion of the interface, rather
than the functions which can be properly namespaced with
autoload#Syntax(), if exposed at all.
|
| | |
| | |
| | |
| | | |
This approach allows more flexibility from the caller's side.
|
| |/
| |
| |
| |
| | |
Only a small subset of option names actually apply, so I'm not entirely
sure this is actually better than nothing.
|
| |\
| | |
| | |
| | |
| | |
| | | |
* hotfix/v0.9.1:
Put missing exclamation mark back into shell check
Bump version number to 0.9.1
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
* hotfix/v0.9.1:
Put missing exclamation mark back into shell check
Bump version number to 0.9.1
Don't report lines deleted after stripping space
|
| | |
| | |
| | |
| | | |
Looks like this was mistakenly omitted in commit 09f8635.
|
| |/ |
|
| |\
| | |
| | |
| | |
| | | |
* feature/silent-whitespace:
Don't report lines deleted after stripping space
|
| |/
| |
| |
| |
| | |
Prepend the line :delete command with a :silent to stop it reporting the
number of lines it removed.
|
| |\
| | |
| | |
| | |
| | | |
* release/v0.9.0:
Bump version number to 0.9.0
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* release/v0.9.0:
Bump version number to 0.9.0
Move 'formatoptions-a' test near applicable block
Precisely define 'formatoptions' 'a' flag presence
Restructure 'format' flag logic around vim-tiny
Map <leader>j to toggle 'fo'-'j' flag in Vim
Use :echoerr not :echomsg for 'fo'-'a' absence
Use simpler error message for 'fo'-'a' absence
Keep script var cache of 'a' 'fo' flag support
Keep script var cache of 'j' 'fo' flag support
Lower threshold for 'formatoptions' 'a' flag
Block 'formatoptions' 'a' flag on old Vim versions
Add 'abort' attribute to autoload function
Add vim/autoload to the lint-vim target
|
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | | |
* feature/vim-fo-a-ver:
Move 'formatoptions-a' test near applicable block
Precisely define 'formatoptions' 'a' flag presence
|
| | |
| | |
| | |
| | | |
Just to keep related things together.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
:help version6.txt, /^Patch 6\.1\.142:
> Patch 6.1.142
> Problem: Defining paragraphs without a separating blank line isn't
> possible. Paragraphs can't be formatted automatically.
> Solution: Allow defining paragraphs with lines that end in white
> space. Added the 'w' and 'a' flags in 'formatoptions'.
> Files: runtime/doc/change.txt, src/edit.c, src/misc1.c,
> src/normal.c, src/option.h, src/ops.c, src/proto/edit.pro,
> src/proto/ops.pro, src/vim.h
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* feature/vim-fo-opt-toggle:
Restructure 'format' flag logic around vim-tiny
Map <leader>j to toggle 'fo'-'j' flag in Vim
Use :echoerr not :echomsg for 'fo'-'a' absence
Use simpler error message for 'fo'-'a' absence
Keep script var cache of 'a' 'fo' flag support
Keep script var cache of 'j' 'fo' flag support
|
| | |
| | |
| | |
| | |
| | |
| | | |
Put in appropriate 'eval' checks and adjust the order of evaluation so
that vim-tiny doesn't try to run all this and fail due to the absence of
'eval' for :let.
|
| | |
| | |
| | |
| | |
| | | |
This is implemented in the same way as done for 'fo'-'a'; testing for
the presence of the flag based on known version tests first.
|
| | |
| | |
| | |
| | |
| | | |
A bit clearer as the mapping was clearly called in error, and results in
not being able to do what was need.
|
| | | |
|
| | |
| | |
| | |
| | | |
Use the result to decide how to map <Leader>a.
|
| |/
| |
| |
| | |
We'll use this in a subsequent commit to decide how to map <Leader>j.
|
| |\
| | |
| | |
| | |
| | | |
* feature/fo-a-vim7:
Lower threshold for 'formatoptions' 'a' flag
|
| |/
| |
| |
| | |
I have found it works correctly on an instance of Vim 7.0.
|
| |\
| | |
| | |
| | |
| | | |
* feature/old-formatopts:
Block 'formatoptions' 'a' flag on old Vim versions
|
| |/
| |
| |
| |
| | |
If I ever care, this needs more careful testing to find the version in
which the flag was added.
|
| |\
| | |
| | |
| | |
| | |
| | | |
* feature/vim-lint-autoload:
Add 'abort' attribute to autoload function
Add vim/autoload to the lint-vim target
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`vint -s` says:
> vim/autoload/detect_background.vim:16:1: Use the abort attribute for
> functions in autoload (see Google VimScript Style Guide (Functions))
All right, then. Doesn't seem to break vim.tiny or Vim 6.1.
|
| |/
| |
| |
| |
| | |
This directory was created in commit 4c46c80, but its contents haven't
been linted with `vint` until now.
|
| |\
| | |
| | |
| | |
| | |
| | | |
* hotfix/v0.8.1:
Actually remove the html5 and targets submodules
Bump version number to 0.8.1
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
* release/v0.8.0:
Bump version number to 0.8.0
|
|\ \ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | | |
* hotfix/v0.8.1:
Actually remove the html5 and targets submodules
Bump version number to 0.8.1
|