From: "Anthony J. Bentley" <firstname.lastname@example.org> To: Ingo Schwarze <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Improper formatting of table with T& Date: Wed, 07 Apr 2021 03:34:51 -0600 [thread overview] Message-ID: <5874-1617788091.947869@oByY.CQsf.WdU3> (raw) In-Reply-To: <YGDo6DpTQu0p3fDY@asta-kit.de> Hi Ingo, Ingo Schwarze writes: > I consider this line a bug in groff; it should be > > +========+=============+===========+=======================+ > > like with mandoc. > ... > If you actually wanted "+--------+------ ...", you would have > to specify > > letter & short for & example & meaning > - > > i.e. a dash rather than an equal sign after the header data. > > Do you agree? Hm, I guess so. I'm not intimately familiar with all the tbl formatting options though. > So, here is a candidate patch. When looking for the last layout row > used, we need to look at the layout row used for the previous data line > containing data, not at the previous data line outright, which might be > a horizontal ruler (as it is in this case). If it is, do not restart > from the first layout row but still proceed to the next data row, which > in this case was just read from T&. > > Does it work for you? Yes, and thanks for the analysis. > If so, is it currently OK to commit to OpenBSD, or is there something > i should pay attention to, such as release preparations or anything > else that might be relevant? No lock yet, although it's probably happening soon. Feel free to commit this with my ok. -- Anthony J. Bentley -- To unsubscribe send an email to email@example.com
prev parent reply other threads:[~2021-04-07 9:35 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-06 4:54 Anthony J. Bentley 2021-03-28 20:36 ` Ingo Schwarze 2021-03-29 0:33 ` Ingo Schwarze 2021-04-07 9:34 ` Anthony J. Bentley [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=5874-1617788091.947869@oByY.CQsf.WdU3 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Improper formatting of table with T&' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).