- Code: Select all
let g:vimwiki_list = [
\ {'path': '~/Dropbox/trunksync/notes/', 'index': 'HomePageVim', 'path_html': '~/trunknotes_html', 'ext': '.markdown', 'auto_export': 1}
\ ]
The basic idea:
- Map the vimwiki path to the trunksync/notes subdirectory in the dropbox area.
- Set the extension to use '.markdown' to match the extension used by trunk notes.
- Specify an index (beginning) page other than 'HomePage', for example 'HomePageVim' (the trunk notes home page doesn't seem to use the .markdown extension so I create my own page and link to that from the trunk box home page).
- Specify a path to the generated HTML (this HTML is what is auto-generated by VIM) which is outside the trunksync directory.
Vimwiki seems to be able to handle trunk notes-generated material reasonably well. You can certainly navigate around between links and view info just fine. Also have tested that creating new pages from vimwiki (followed by automatic dropbox sync and then sync from trunk box) makes them appear in trunk box linked in the expected place with the expected content.
If you stick to a fairly limited subset of content (areas where they do things the same, like lists and links) it is workable. What I'm doing so far is treating Trunk Notes as the master format and then just using vimwiki on the other machine to add basic content and new pages. In VIM, I can use the same markup format as trunk notes -- since you stay in the non-rendered environment most of the time in vimwiki anyway, it doesn't really matter much that you are using trunk notes markup within the wiki pages themselves since the most important elements match (e.g., camelcase links, links of the form [[ThisIsAPage|link to a page]]).
Haven't used it extensively yet, so can't say what the caveats may be: try at your own risk.
