discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Abhinav Upadhyay <er.abhinav.upadhyay@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mdocml.bsd.lv, Thomas Klausner <wiz@netbsd.org>
Subject: Re: Mandoc Not Parsing Sy Macro (In some cases)
Date: Tue, 10 Jan 2017 20:20:20 +0530	[thread overview]
Message-ID: <CAHwRYJnotiGAT7BSSxTBPmY4mZVc8TUbCJFZOkPFVXSi=DLwiw@mail.gmail.com> (raw)
In-Reply-To: <20170109134025.GD94305@athene.usta.de>

On Mon, Jan 9, 2017 at 7:10 PM, Ingo Schwarze <schwarze@usta.de> wrote:
> Hi Abhinav,
>
> Abhinav Upadhyay wrote on Mon, Jan 09, 2017 at 04:06:43PM +0530:
>
>> Whereas in the places where it was being rendered correctly, we were
>> using Ta, like this:
>>
>> It Sy Name  Ta Sy Constant     Ta Sy Next level names Ta Sy Description
>
> Yes, that is exactly why you should preferably use Ta and not
> literal tabs.  It's much easier to use correctly, and the mdoc(7)
> source code is easier to read.
>
> If you insist on using literal tabs, you need a blank character
> between the tab and the following macro.
>
> Yes, that is weird: a blank is syntactically significant after
> a tab.  But that's just how roff traditionally behaves.

Ah, I wasn't aware of it, and it is also quite difficult to catch :)

>
>> I think this issue was not present in the previous version of mandoc,
>
> Yes, 1.13.3 had a bug processing the first word after a tab
> incorrectly.  It was fixed on October 17, 2015.
>
> See
>
> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/regress/usr.bin/mandoc/mdoc/Bl/column.in
>
> in particular the commit message of revision 1.8, the test code
> added by that commit, and the correct output in
>
> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/regress/usr.bin/mandoc/mdoc/Bl/column.out_ascii?rev=HEAD&content-type=text/x-cvsweb-markup
>
>> It has been noticed only with the latest release.
>
> The proper response is to fix your manual pages.  You should do that
> because as they are, they are not portable and won't work with groff.
> Either insert the missing blanks or - much better for clarity
> and robustness - use Ta rather than bare tabs.

Yes, we have already changed to using Ta.

> I think i will also commit a clarification to the mdoc(7) manual
> because this is indeed a nasty trap for the unwary.

Thanks :)

-
Abhinav
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

      parent reply	other threads:[~2017-01-10 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09 10:36 Abhinav Upadhyay
2017-01-09 13:40 ` Ingo Schwarze
2017-01-09 14:18   ` Ingo Schwarze
2017-01-10 14:50   ` Abhinav Upadhyay [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='CAHwRYJnotiGAT7BSSxTBPmY4mZVc8TUbCJFZOkPFVXSi=DLwiw@mail.gmail.com' \
    --to=er.abhinav.upadhyay@gmail.com \
    --cc=discuss@mdocml.bsd.lv \
    --cc=schwarze@usta.de \
    --cc=wiz@netbsd.org \
    --subject='Re: Mandoc Not Parsing Sy Macro (In some cases)' \
    /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).