On Fri, 13 Nov 2020 13:43:56 +0100
Tadziu Hoffmann wrote:
> > element of set is '\[mo]'. Would it still be logical to expand
> > the synax for eqn to add it as a keyword?
>
> I would just put something like
>
> define member % type relation \[mo] %
> define emptyset % \[es] %
>
> and
> edit: ~/.groff/eqnrc
> define eqnrc_version % 0.0 %
>
> and got "define eqnrc_version % 0.0 %" literally included on top of
> the created .ps-file.
Despite the name, eqnrc can contain all sorts of troff input,
not only stuff for eqn, and is simply inserted into input stream.
Material for eqn
On Fri, 27 Nov 2020 15:17:49 +0100
Tadziu Hoffmann wrote:
> > edit: ~/.groff/eqnrc
> > define eqnrc_version % 0.0 %
> >
> > and got "define eqnrc_version % 0.0 %" literally included on top of
> > the created .ps-file.
>
> Despite the name, eqnrc can contain all sorts of troff input,
> not
> eqn does well, however .PS/.PE doesn't seem to be processed by [g]pic
> on inserting.
>
> I compiled using: groff -e -p test.groff > test.ps
The eqnrc is inserted by eqn, but in the pipeline run by
"groff -e -p", eqn runs *after* pic, so pic never sees this input
and cannot act upon it. Since
