Hi. here [1] you find references of literalinclude. IMHO you may follow tutorial, build something what you think and after make some testes using literalinclude and proof or not what you think? for understand what and how sphinx read files look at github sphinx source code or compile and create sphinx rich documentation that doxygen,sphinx produce, this make more easy cross reference, index, classes, etc.
[1] http://sphinx-doc.org/index.html 2015-11-25 14:46 GMT-02:00 Andrea Cassioli <[email protected]>: > Hi, > I am not sure what kind of code or poc would be needed in my case. I guess > my question is quite simple and mainly focused on how Sphinx works. Let me > restate: > > Does literalinclude perform any kind of caching in the case a file appears >> to be read more than once? >> > > For example, you may first show a bunch of line, then others. Does Sphinx > read the file twice? > > On Thursday, April 16, 2015 at 1:34:03 PM UTC+2, Andrea Cassioli wrote: > >> It may be a silly question, but I was wondering whether literalinclude >> (or the like) performs some kind of caching when reading files. I mean, if >> I read the same file twice in my docs, will it be cached somehow? >> > -- > You received this message because you are subscribed to the Google Groups > "sphinx-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sphinx-users. > For more options, visit https://groups.google.com/d/optout. > -- gilberto dos santos alves +55(11)9-8646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "sphinx-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sphinx-users. For more options, visit https://groups.google.com/d/optout.
