>
> There have been suggestions to move all code-documenting directives into
> a namespace of sorts, i.e. "code.class", "code.function" etc. This doesn't
> appeal to me very much; it sounds like a complication where none is needed,
> and doesn't lead to nice to read markup.
I don't know how it would be implemented, but namespacing suggests
itself as the most obvious technical solution for this kind of
problem.
speculative +1 namespaces
It also has the disadvantage that
> *all* existing directives will have to go. Still, if enough people are in
> favor...
>
There is that - but it's not version 1.0 yet...
>
> PS: My other suggestion of an extensions repository has only been given
> one +1, so I think I'll just create it and see :)
+1 sphinx-contrib
+1 sphinx-themes
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
