Closes#769.
Also fixes an error when adding missing '.' to mapped extensions. The
previous behavior tried to access a value after it was removed from the
dictionary.
The instructions to loading MathJax from a CDN were outdated and not
working for some users.
This commit updates those links to conform with the instructions from:
https://www.mathjax.org/#gettingstarted
- 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
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
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.
Fixes#240. Also fixes a related issue where markdown links where not
correctly highlighted in todo lists. Adds concealment for markdown links
in todo lists.
All key mappings have the option of being disabled but the <Plug>
definitions are still available for user customization. Key sequences
are no longer overwritten if a mapping already exists. Fixes#671,
fixes#425.
Vim used to throw the E706 error if you tried to change a variable's
type. This error can be triggered by vimwiki if, during the user
settings loop in `read_global_settings_from_user()`, the variable type
for `users_value` changes.
The vim error was removed in v7.4.1546 as part of
f6f32c38bf.
Changing this option to allow empty strings places the diary files in the same directory as the main wiki files. This is more backwards compatible with previous releases.
Names can be used for interwiki links in the format wn.name:link.
Additionally, :VimwikiUISelect and the menu created in GVim utilize the
wiki name. Fixes#612, closes#477.
* Temporary fix for omnicomplete of vimwiki links - #456.
This fixes the omnicomplete of wiki links under Windows which were
not working since paths on Windows use '\' instead of '/'. This is
a temporary fix until path refactoring is done.
* Update changelog with description of fix for #456
This adds the vimwiki_local `html_filename_parameterization` option (0|1)
which performs the same sanitization of filenames as does the
vimwiki_markdown gem.
For example, if your file is called "My File.md" it will be written out
as "my-file.html".
If the html_filename_parameterization options is enabled, we also _do
not delete_ non-matching html files when the VimwikiAllToHtml command is
run.
Closes#129
Adds new configuration variable, "conceal_onechar_markers", defaulting
to on (preserving default behaviour)
Adds if-statement around relevant parts of code (as suggested in the
issue), which uses the new configuration variable.
Fix#315 - Don't conceal one-character markers
The wikilocal option links_space_char will be used to replace any spaces
when creating a new wiki link and page. This only affects link creation
with a visual selection.
Commands such as :VimwikiIndex and :VimwikiDiaryIndex did not previously
take a count and the doucmentation was inconsistent/incorrect for the
behavior of these commands. Fixes#543.
