Hola!
Google code closes "Downloads" and thus we wouldn't be able to distribute vimwiki releases the way it was. On the other hand there are other ways to distribute vim plugins available: pathogen or vundle. Plus github.com, where one can find vast majority of vim plugins as a separate repos or united under vim-scripts's mirror. Not to mention there is an easy way to download zipped vimwiki sources which is practically the same as vimwiki-2-1.zip we have at "Downloads" tab.
So meet https://github.com/vimwiki/vimwiki
--
You received this message because you are subscribed to the Google Groups "vimwiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vimwiki+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
First question: Einfach, can you let us know what the differences are in your branch, or, if you changed the docs, where to look there for the differences? I am looking at the file diffs, but I am not at all sure I am understanding everything.
Secondly: this raises a more general question, for anyone to answer. Assuming that one wants to experiment with vimwiki branches, what would be the Correct way of installing / uninstalling branches without risking losing data? I have an inkling that because it is now on githup, pathogen would be the right way to deal with this. I've installed a few other plugins with pathogen, but my vimwiki was, I believe, a manual install, old style. Should I just scour my ~/.vim/ for anything that is *wiki, and do a pathogen install? Surely there must be a better method. Any thoughts?-- Steen