bug-groff
[Top][All Lists]
Advanced

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

[bug #64575] [PATCH] doc/pic.ms: document .PY


From: G. Branden Robinson
Subject: [bug #64575] [PATCH] doc/pic.ms: document .PY
Date: Tue, 22 Aug 2023 11:49:28 -0400 (EDT)

Update of bug #64575 (project groff):

                  Status:                    None => In Progress            
             Assigned to:                    None => gbranden               

    _______________________________________________________

Follow-up Comment #1:

Hi Dave,

[comment #0 original submission:]
> * Changes the .PY definition in tmac/pic.tmac to call to .PF rather than
duplicating its (three bytes of) code.  This is almost too trivial to DRY,
but
> ** the new form is a cue to the human reader that .PY is meant to be an
alias of .PF; and
> ** .PE was already defined as a variant of .PF with an explicit call to it,
so this makes the .PY definition conform to that precedent.

I must have mistakenly thought that `PY` would call _mm_'s `PF`, but
experimentation reveals that this is not the case.

You can load `pic.tmac` before or after _mm_, or not at all (this is
preferred, since _mm_ provides its own implementations).


groff -p -mm -mpic # bad idea


clobbers _mm_'s macros of the same names (taking the `PF` page footer
management macro off the table), and changes the rendering (because "pic.tmac"
centers pictures and _mm_ doesn't), but otherwise seems to do no damage--to a
trivial document like the following.


$ cat EXPERIMENTS/little-flyback-pic.mm
.P
Check this out.
.P
.PS
circle 2i filled
.PY
I dug a hole!


_groff mm_ *does* have internal macros that call `PF`, so I think the advice
in _groff_tmac_(5) on this subject holds.

No objection to your patch--just preserving this little exploration for
posterity and searchability.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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