Yea, I was just ignoring the warning message.

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.

On Mon, Mar 29, 2010 at 12:30 PM, Max Battcher <[email protected]> wrote:
> TP wrote:
>>
>> Additionally, in the latest trunk revision, the unused_docs conf.py
>> option no longer works, so if you change the name back to include .rst,
>> you then get the "WARNING: document isn't included in any toctree"
>> message.
>
> That warning is certainly harmless, if that's your biggest concern against
> using .rst as the file extension. In an earlier thread Georg mentioned that
> maybe it was time that warning was rewritten or rethought, because it looks
> scarier than it is intended to be. From what it appears to me, it's meant to
> be something of a "Hey, did you know you didn't add this file to your
> toctree?" reminder than a "Whoops, things are broken because you have a
> document that you haven't put into a toctree." I think that maybe the
> documentation you cited should be rewritten as well.
>
> --
> --Max Battcher--
> http://worldmaker.net
>
> --
> 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.
>
>

-- 
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