On Fri, Feb 23, 2024 at 03:25:05PM +0100, Alejandro Colomar wrote:
> On Fri, Feb 23, 2024 at 03:20:58PM +0100, Alejandro Colomar wrote:
> > So, how do you get that "-dirty" suffix? Is it autotools? Or git? Or
> > is it specific to the groff build system? I could use some shell code
> > in the m
On 2/22/24, G. Branden Robinson wrote:
> I've come to think that a set of "best practice" for *roff document
> composition is to:
>
> A. Load your desired full-service macro package (if any) on the command
> line with `-m`.
> B. Load any auxiliary macro packages that your document _requires_
On Fri, Feb 23, 2024 at 03:20:58PM +0100, Alejandro Colomar wrote:
> Hi Branden,
>
> I notice that when I build groff(1) from source, it gets its version
> from git(1), and if the repository is dirty (has modifications on top of
> the last commit), the version string has a "-dirty" suffix.
>
> I
Hi Branden,
I notice that when I build groff(1) from source, it gets its version
from git(1), and if the repository is dirty (has modifications on top of
the last commit), the version string has a "-dirty" suffix.
I was wondering how you get the version string, because I'd like to use
that "-dirt
