- Create function wrapper around lvimgrep for input checking, pattern
quoting, and error handling.
- Add Vader tests for VimwikiSearch.
- Change syntax loading from try/catch to explicit file check (to
prevent Vader test bug).
- Update doc/vimwiki.txt for changes.
- Change test script to run Vader tests separately
Previously a new list marker would get added when working within a code
block that was part of a list. This change excludes code blocks from
list marker creation.
This change ensures the syntax is properly changed when running multiple
tests by removing the previously created temporary wiki and then
creating a new one.
This change modifies the behavior of VimwikiReturn to not insert a new
list marker if not within a list. Mostly useful when mapping <CR> to
VimwikiReturn 3 5 or similar. The behavior of 'o' was also modified to
properly insert a marker in a list with hard line wraps.
This is necessary to properly allow the user to remap these since there
are different arguments to the command. The documentation regarding this
command was also updated to be more clear.
This commit changes the autocmd registration in vimwiki so that
registration happens once rather than once per extension.
Instead of the following,
autocmd BufEnter *.md call s:setup_buffer_enter()
autocmd BufEnter *.mdown call s:setup_buffer_enter()
We'll now only run,
autocmd BufEnter *.md,*.mdown call s:setup_buffer_enter()
This probably has no effect on performance but it makes for a simpler
implementation.
The functions stopped at the end/start block marker (respectively)
instead of returning the following line. This caused issues when the
function was subsequently called in markdown mode since the start and
end block markers are the same.
This fixes#407
For markdown syntax the extension was added to the url multiple times if
the option g:vimwiki_markdown_link_ext was set which is now fixed.
Normalizing links no longer adds the extension to the description field.
This change makes the horizontal rule syntax more closely match the
commonmark spec https://spec.commonmark.org/0.29/#thematic-breaks. The
number of characters required was changed to 3 and '___' and '***' where
added as valid sequences. The space rules were not added becuase it adds
extra complexity for little benefit. Issue #664.
