On Sun, Jun 28, 2009 at 6:56 AM, TL <[email protected]> wrote:
>
> The rST specification defines an "include" directive that can take a
> absolute or relative path to a text file that will be inserted into
> the source code at that location (same functionality as the C
> language's #include directive). Support for specifying a relative
> path appears to be broken. I assume this is because the file
> submitted to the docutils module is not located in a directory
> associated with the project such as the directory defined by the rst3
> plugin's "default_path" configuration item. Correct? If so, is it
> possible to change the rst3 plugin's implementation to utilize the
> "default_path" or create a new "submit_path" configuration item.
Presumably, if any adjustment is needed, it will be to writeToDocutils in
leoRst.py (in leoPy.leo)
There is only one call to docutils::
# All paths now come through here.
res = docutils.core.publish_string(source=s,
reader_name='standalone',
parser_name='restructuredtext',
writer_name=writer,
settings_overrides=overrides)
My guess is that settings_overrides is the one and only way to get the job
done. I could be wrong.
Looking at the code, there are several clauses that add to the overrides
dict. I would be happy to add more, if I knew exactly what you wanted.
Edward
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" 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/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
