On 16 July 2013 20:31, Terry Jones <[email protected]> wrote: > Hmmmm, maybe I wasn't hallucinating after all! Thanks Steven. Sounds like > the lack of file content manages to trick asciidoc into thinking breadth is > depth. > > Terry > > @Stuart,
self.open() called at line 4219 calls Reader1.read() which finds no more to read so calls Reader1.eof() which backs self to parent all before current_depth is incremented at line 4220. So current_depth is incremented in the wrong version of self. @Steven, thanks for the details, that made it possible to track down. For the moment I guess everyone just has to include something, not an empty file :) Cheers Lex > > > On Tue, Jul 9, 2013 at 10:18 PM, Steven Clark <[email protected]> wrote: > >> Just to add some more data: I experienced a similar issue. To give some >> background on my structure, I have a main file with some variable settings, >> and that includes a "contents" file, which includes several "section" >> files. "Section" files include other files, but that is the maximum include >> depth; those files generally do not include other files, except on >> occasion. Two section files were generating warnings of "maximum include >> depth exceeded". The files in question include many files, some of which >> are completely empty (created using 'touch'). When I added content to those >> files (I went for "real" content, as opposed to adding a blank line, since >> I had do to the work anyway; not sure if this played a role). This resolved >> the warnings. >> >> Since I'm not satisfied with just dumping out this vague anecdotal info, >> I decided to try something a little more formal. >> >> This is with AsciiDoc 8.6.8, running under Cygwin. >> >> I created a file called "sample.txt", and it contains the text "Foo", >> plus lines that look like: >> include::s1.txt[] >> >> repeated, for the numbers 1-12, all separated by spaces. The include >> files were created using 'touch'. ls -l reports them as having 0 bytes. >> asciidoc.py run on this file generates: >> >> asciidoc: WARNING: sample.txt: line 23: maximum include depth exceeded >> asciidoc: WARNING: sample.txt: line 25: maximum include depth exceeded >> >> The two lines are the last two includes in the file. If I modify s1.txt >> to contain a single space (ls -l now reports 3 bytes), this is the result: >> >> asciidoc: WARNING: sample.txt: line 25: maximum include depth exceeded >> >> And if I modify s4.txt, it fixes the line 25 warning. A minor issue, >> since it can be corrected by adding data to the file, but here it is. >> >> By the way, thanks for a useful product, Stuart! >> >> Regards, >> -- Steven C. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "asciidoc" 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/asciidoc. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > You received this message because you are subscribed to the Google Groups > "asciidoc" 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/asciidoc. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "asciidoc" 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/asciidoc. For more options, visit https://groups.google.com/groups/opt_out.
