bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #62801] [me] doc/meref.me.in: `2c`'s first argument can be empty


From: G. Branden Robinson
Subject: [bug #62801] [me] doc/meref.me.in: `2c`'s first argument can be empty
Date: Thu, 6 Oct 2022 00:52:53 -0400 (EDT)

Update of bug #62801 (project groff):

                  Status:               Confirmed => Need Info              

    _______________________________________________________

Follow-up Comment #7:

I _believe_ this is addressed now through material in the introduction and a
much more disciplined practice of declaring default values when registers and
strings are introduced.


$ ./build/test-groff -me -Tascii ./build/doc/meref.me
[...]
     Many  of  the package's rendering parameters can be ad-
justed through registers, strings, and macro  calls.   Macro
arguments  are  denoted  with  lowercase letters for numeric
values (suffixed with a scaling  unit  if  appropriate)  and
with uppercase for text arguments.  Default parameter values
are  shown in square brackets.
[...]
6.  Columnated Output

.2c +-s n              Enter  multi-column  mode, formatting
                       text in n [2] columns of equal width.
                       The column separation  ("gutter")  is
                       set  to +-s [4n], saved in \n($s, and
                       persists until changed by this macro.
                       The n columns with n-1  gutters  fill
                       the  single-column  line length; each
[...]
                       column's line  length  is  stored  in
                       \n($l.   The current column number is
                       in \n($c and the number of columns in
                       \n($m.
[...]


Between the above and the stipulation to which we agreed in comment #2, I
think the reader can infer from this that


.2c "" 3


is valid input, and will preserve the pre-existing (or package default) gutter
width.

What do you think?


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]