One9398 / vimwiki

Automatically exported from code.google.com/p/vimwiki
0 stars 1 forks source link

Relative path for HTML output #388

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
I maintain wikis in different directories and open them by explicitly passing 
their index files to vim. So say .../some/path/index.wiki. When I generate HTML 
via :Vimwiki2HTML, it's output in a directory .../some/path_html. I'd like this 
directory to be .../some/path/html. There does not appear to be an easy way to 
configure this; is there? It would also be nice to keep templates at a relative 
path, maybe .../some/path/html/templates.

Original issue reported on code.google.com by fox...@gmail.com on 27 Nov 2012 at 12:16

GoogleCodeExporter commented 8 years ago
You can register wiki's as described under ":h vimwiki-register-wiki" in order 
to specify the 'path', 'path_html', and 'template_path' variables.

  let g:vimwiki_list = [{'path': '/some/path/',
          \ 'path_html': '/some/path/html/',
          \ 'template_path': '/some/path/html/'}]

You will probably pick-up a thing or two by revisiting the docs from time to 
time.

Original comment by stu.andrews on 28 Dec 2012 at 3:22

GoogleCodeExporter commented 8 years ago
I read that in the docs before posting the issue. The request is quite 
specific: relative paths. I don't think they are supported right now. I don't 
want to specify an explicit initial 'path'. Why can't I say where I want html 
output relative to where the wiki file is?

Original comment by fox...@gmail.com on 28 Dec 2012 at 3:27

GoogleCodeExporter commented 8 years ago
Good point.  Wiki-registration is an aspect of vimwiki that is a bit awkward. 

I have done some preliminary work that allows one to register a wiki by placing 
a vimwiki.vimrc file in the root of the wiki itself.  In theory, it should 
allow paths to be specified relative to this location.  I'll look into adding 
this feature.

Thx.

Original comment by stu.andrews on 28 Dec 2012 at 3:03