From: David Goodger <goodger@py...> - 2003-07-29 03:59:53
Brett g Porter wrote:
> ...but then I want to be able to do
> ``SOME_USEFUL_STRUCT structData;``
> bla bla bla
> ...and have the text of SOME_USEFUL_STRUCT be a clickable link to
> the documentation of that structure.
> ...or maybe a role?:
> :parsed-literal:`SOME_USEFUL_STRUCT_ structData;`
Yes, a role would seem to be the solution. Care to implement it?
> I can't seem to mix parsed-literal blocks and definition lists.
Definition list terms can only be one line long, and they must be
simple text with no structural markup. The second, indented line is
what triggers "definition list" recognition in the parser. A
parsed-literal block, even if only one line, by definition contains
structural markup: the ".. parsed-literal::" text is not simple text,
but a directive. And any indented second line would automatically be
subsumed into the directive's content. So that approach is doomed in
multiple ways. ;-)
David Goodger http://starship.python.net/~goodger
For hire: http://starship.python.net/~goodger/cv
(includes reStructuredText: http://docutils.sf.net/rst.html)