[bug #62801] [me] doc/meref.me.in: Clarify a couple points about empty macro arguments

[Dave]

URL:
  <https://savannah.gnu.org/bugs/?62801>

                 Summary: [me] doc/meref.me.in: Clarify a couple points about
empty macro arguments
                 Project: GNU troff
               Submitter: barx
               Submitted: Fri 22 Jul 2022 04:08:18 PM CDT
                Category: Macro me
                Severity: 1 - Wish
              Item Group: Documentation
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Fri 22 Jul 2022 04:08:18 PM CDT By: Dave <barx>
A few -me macros (.ip, .sh, .$p, .2c since commit 01cf10eb
<http://git.savannah.gnu.org/cgit/groff.git/commit/?id=01cf10eb>, probably
others) accept empty arguments, but the _me Reference Manual_ doesn't say how
to pass an empty argument to a roff macro.  The full troff manual does, or
probably most users can figure it out with a couple of guesses, but the -me
manual may as well have a sentence in the introductory material to spell it
out, since the macro set does make use of the capability.

In the wake of the aforementioned commit, it may also be worth having the .2c
description explicitly say that this macro can accept an empty first argument.
 Bug #61671, which precipitated this commit, notes that the manual didn't
forbid it before, prompting the change, but it still doesn't expressly endorse
it either, which it perhaps should now that it's specifically supported.

(That bug's comment 2--made after the bug was already closed, giving it low
visibility--also notes a minor indentation issue in the commit.  This is not
strictly related to the documentation issue noted above, but as an adjacent
issue that's not really worth opening up a new bug report for, I note it
here.)







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62801>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/