Fernando Perez wrote:
> I renamed it because there's a bit of a conflict with the current
> 'plot' directive, which allows a filename *or* a content block, but in
> that case the content block is meant to be the source code, as
> illustrated in sampledoc:
>
> http://matplotlib.sourceforge.net/sampl
Fernando Perez wrote:
> I renamed it because there's a bit of a conflict with the current
> 'plot' directive, which allows a filename *or* a content block, but in
> that case the content block is meant to be the source code, as
> illustrated in sampledoc:
>
> http://matplotlib.sourceforge.net/sampl
Hi Michael,
On Mon, Sep 14, 2009 at 6:57 AM, Michael Droettboom wrote:
> I'm not sure it's that bad. It's certainly possible to do all these things
> with a single directive, since providing a path or providing source code is
> mutually exclusive. The thing one can't do is provide inline source