aditya siram writes:
> Thanks, but I was hoping there was some way of including that in the
> exported HTML/PDF etc. That way someone looking at the documentation can
> find their way back to the source file. As it stands (at least with the
> HTML exporter) there's no way to know where a chunk of
Dnia 2013-10-18, o godz. 09:47:47
aditya siram napisał(a):
> Hi all,
> Currently when I export a literate program I can see the chunks but
> not where they end up. It would be really useful if the chunks had a
> footnote or something that linked to the file where they were
> tangled. Is there a h
Thanks, but I was hoping there was some way of including that in the
exported HTML/PDF etc. That way someone looking at the documentation can
find their way back to the source file. As it stands (at least with the
HTML exporter) there's no way to know where a chunk of code ends up.
-deech
On Fri,
aditya siram writes:
> Hi all,
> Currently when I export a literate program I can see the chunks but not
> where they end up. It would be really useful if the chunks had a footnote
> or something that linked to the file where they were tangled. Is there a
> header argument that does that?
>
> Tha
Hi all,
Currently when I export a literate program I can see the chunks but not
where they end up. It would be really useful if the chunks had a footnote
or something that linked to the file where they were tangled. Is there a
header argument that does that?
Thanks!
-deech
