Small cleanup of the merged PR

Ref #187
This commit is contained in:
EinfachToll 2016-01-28 10:52:40 +01:00
parent 2aeaea5f0d
commit 5f9dbca89c
2 changed files with 16 additions and 8 deletions

View File

@ -1972,7 +1972,7 @@ function! vimwiki#base#detect_nested_syntax() "{{{
\ 'substitute(v:val, last_word, "\\=submatch(1)", "")') \ 'substitute(v:val, last_word, "\\=submatch(1)", "")')
let dict = {} let dict = {}
for elem in lines for elem in lines
exe "let dict.".elem." = elem" let dict[elem] = elem
endfor endfor
return dict return dict
endfunction "}}} endfunction "}}}

View File

@ -2017,16 +2017,24 @@ or in: >
*vimwiki-option-automatic_nested_syntaxes* *vimwiki-option-automatic_nested_syntaxes*
------------------------------------------------------------------------------ ------------------------------------------------------------------------------
Key Default value~ Key Default value~
automatic_nested_syntaxes 1 automatic_nested_syntaxes 1
Description~ Description~
Allows for smaller |vimwiki-option-nested_syntaxes| dictionaries, by turning If set, the nested syntaxes (|vimwiki-option-nested_syntaxes|) are
entry for python on the previous example unnecessary: > automatically derived when opening a buffer.
let wiki.nested_syntaxes = {'python': 'python', 'c++': 'cpp'} Just write your preformatted text in your file like this >
{{{xxx
my preformatted text
}}}
It requires that the file is reloaded (|:edit|) after new |filetype| is where xxx is a Vim filetype.
included in a file.
Note that you may have to reload the file (|:edit|) to see the highlight.
Since every file is scanned for the markers of preformatted text when it is
opened, it can be slow when you have huge files. In this case, set this option
to 0.
*vimwiki-option-diary_rel_path* *vimwiki-option-diary_rel_path*