Re: [Groff] Several file arguments to groff

[Werner LEMBERG]

> > [...] the main reason is not groff but the function used to parse
> > the command line arguments: GNU's getopt.  It sorts options and
> > non-options (the latter coming first).  For the above command
> > line, groff sees this:
> > 
> >   groff -man -me -ms -Tlatin1 man/groff.man doc/meintro.me doc/pic.ms
> >
> If getopt() is replaced by a better option handler, would that be
> enough for groff to generate a suitable output for all such kinds of
> files with different macro packages?

No.  All macro packages had to be rewritten to be cooperative.

In general, I don't see why we should do such a thing.  Who needs that
feature (except man/mdoc)?  What benefit do we have?  I believe we
are discussing a theoretical question without a practical use.


    Werner