On Wed, Mar 5, 2025 at 5:35 AM Markus Armbruster <arm...@redhat.com> wrote:
> John Snow <js...@redhat.com> writes: > > > This is for the sake of the new rST generator (the "transmogrifier") so > > we can advance multiple lines on occasion while keeping the > > generated<-->source mappings accurate. > > > > next_line now simply takes an optional n parameter which chooses the > > number of lines to advance. > > > > RFC: Here's the exorbitant detail on why I want this: > > > > This is used mainly when converting section syntax in free-form > > documentation to more traditional rST section header syntax, which > > does not always line up 1:1 for line counts. > > Obvious way to resolve the RFC: > > The next patch will use this when converting ... > > > > > For example: > > > > ``` > > ## > > # = Section <-- Info is pointing here, "L1" > > # > > # Lorem Ipsum > > ## > > ``` > > > > would be transformed to rST as: > > > > ``` > > ======= <-- L1 > > Section <-- L1 > > ======= <-- L1 > > <-- L2 > > Lorem Ipsum <-- L3 > > ``` > > Not a demand, just wondering: could we drop our headings syntax and just > use rST? > Yes, once we drop the old qapidoc fully, which I am not sure I can do before freeze ... So we have some goofy stuff in the meantime. You suggested before I can rewrite the freeform generator to avoid needing this; I wrote the freeform generator to be as close to the old one as I could, but we could kerjiggle it if needed. ... On the other hand, this is a patch for a += n, so... eh. --js
