Hi TP.

I tried the same, but its not that easy!

When docutils generates warnings, I found that the generated warnings
were always at an offset.
e.g. docutils says error at line 10, but physically, its line 2 in
your .rst file.

BR,
Purnank


On Mar 30, 5:35 pm, TP <[email protected]> wrote:
> I implemented rst_prologue option in conf.py 
> here:http://bitbucket.org/tpowers/sphinx/changeset/c5ad17aa65cb/(it's only
> a few changed lines).
>
> On Mon, Mar 29, 2010 at 7:29 PM, Fernando Perez <[email protected]> wrote:
> > On Mon, Mar 29, 2010 at 2:42 PM, TP <[email protected]> wrote:
>
> >> However, as described in my "Include directive doesn't correctly support
> >> 'absolute' paths" message, includes seem to be useless when used from
> >> multiple subdirs in the same project.
>
> >> Unless I'm missing something, there doesn't seem to be any easy way to
> >> use the same include directive from multiple subdirs. You might be able
> >> to use different 'relative' paths depending on where you are including
> >> from but that seems more bother than it's worth.
>
> >> Instead, for now, I'll just implement a rst-prologue conf.py option
> >> (analogous to the rst-epilog option) and avoid includes altogether.
>
> > My (hackish, ugly but functional) solution to this is to use
>
> > include: foo.txt
>
> > and in *every* directory (but the project topmost one, of course),
> > have a symlink
>
> > foo.txt -> ../foo.txt
>
> > so they eventually all resolve at the top.  Not pretty, but works for me :)
>
> > Cheers,
>
> > f
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "sphinx-dev" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to 
> > [email protected].
> > For more options, visit this group 
> > athttp://groups.google.com/group/sphinx-dev?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sphinx-dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sphinx-dev?hl=en.

Reply via email to