tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: Add support for `OP', one of the extended man macros.
Date: Sun, 26 Feb 2012 20:55:20 +0100	[thread overview]
Message-ID: <20120226195520.GK5977@iris.usta.de> (raw)
In-Reply-To: <201201031516.q03FGP2k006780@krisdoz.my.domain>

Hi Kristaps,

kristaps@mdocml.bsd.lv wrote on Tue, Jan 03, 2012 at 10:16:25AM -0500:

> Log Message:
> -----------
> Add support for `OP', one of the extended man macros.  This also requires
> some man(7) changes to accomodate for the an-ext compatibility.
> 
> Modified Files:
> --------------
>     mdocml:
>         man.7
>         man.c
>         man.h
>         man_html.c
>         man_macro.c
>         man_term.c
>         man_validate.c

I have just merged this to OpenBSD, with one small tweak (see below).

I agree that we should support GNU extensions for compatibilty
if they occur in practice and unless they cause too much bloat;
but i insist in discouraging their use more strongly.

Obviously, esr was very misguided in proposing these extensions.
He combines the worst parts of both worlds:  The clunkyness of
the ancient man(7) macros, which cannot be repaired by adding
a few more macros, and the portability problems still haunting
mdoc(7).  If man(7) has any excuse to still exist, it's
portability, and man-ext clearly gives that last asset away.

So, we should handle these macros as deprecated, not list them
in the MACRO OVERVIEW, and prominently discourage their use
up front, not only below COMPATIBILITY where the warning can
easily be missed.

OK to commit this tweak to bsd.lv as well?

Yours,
  Ingo


--- /co/mdocml/man.7	Wed Jan  4 03:24:13 2012
+++ ./man.7	Sun Feb 26 20:41:27 2012
@@ -272,10 +272,6 @@
 .It Sx RB Ta alternate between roman and boldface fonts
 .It Sx RI Ta alternate between roman and italic fonts
 .El
-.Ss Semantic markup
-.Bl -column "PP, LP, P" description
-.It Sx OP Ta optional arguments
-.El
 .Sh MACRO REFERENCE
 This section is a canonical reference to all macros, arranged
 alphabetically.
@@ -443,7 +439,8 @@
 .Sx \&TP .
 .Ss \&OP
 Optional command-line argument.
-This has the following syntax:
+This is a non-standard GNU extension, included only for compatibility.
+It has the following syntax:
 .Bd -filled -offset indent
 .Pf \. Sx \&OP
 .Cm key Op Cm value
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

       reply	other threads:[~2012-02-26 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201201031516.q03FGP2k006780@krisdoz.my.domain>
2012-02-26 19:55 ` Ingo Schwarze [this message]
2012-03-27 13:58   ` Kristaps Dzonsons

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=20120226195520.GK5977@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=tech@mdocml.bsd.lv \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).