Hey Andrey,
> I just fixed a couple of format problems in documentation (using git in > case it matters) and had two problems with the way docbuid works: > > 1. There is no message about warning in the end of the output. As the > process takes a while, I am not watching what's going on and when I come > back to the terminal I see a lot of statistics but have to scroll up and > search for warnings/errors. Would be way better if they were summarized in > the end as it is done with doctests. > In care you are unaware, I would recommend doing a more narrow docbuild with "reference/subsection" where subsection is for example combinat or algebras. Also on the next time you're rebuilding the doc, it should only print about what files were changed, so it shouldn't be too far to scroll. IDK, I guess what I'm saying is I've never really thought that this was an issue. > 2. Line numbers are completely screwed up - I could not figure out what is > wrong with 4 and 14, because they both were in the second thousand far away > from each other. I ended up looking through the whole file. > > Is this something known or does anybody know how to fix it? I am pretty > sure that line numbers used to be correct. > > As Volker stated, it's relative to the start of the docstring, but it would be nice to have some absolute positioning in the file. IMO the best method to figure out where a docstring problem is to look through the output as they tend to make a portion be clearly misformatted. Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
