Re: [bug #68597] doc/ms.ms.in: document does not render correctly in groff 1.25.0.rc2

Morten Bo Johansen <[email protected]>
Newsgroups gmane.comp.printing.groff.general
Message-ID <[email protected]>
On 2026-08-04 G. Branden Robinson wrote:

> Setting to "Need Info" because we need feedback from Morten.  What does "groff
> --version" say?

   ~/ % groff --version
   GNU groff version 1.25.0.rc2
   Copyright 1989-2026 Free Software Foundation, Inc. and others
   
   This is free software, distributed under the terms of the GNU General Public
   License, version 3, or any later version, at your option.  There is NO warranty;
   not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
   
   See the "COPYING", "FDL", and "LICENSES" files in the groff distribution or
   package for additional notices and permissions.
   
   programs in constructed pipeline:
   
   GNU grops (groff) version 1.25.0.rc2
   GNU troff (groff) version 1.25.0.rc2


>   Unless "." comes early in your path--which is a known security
>   exploitation vector, don't do that--this command:
>
>
> ~/ % groff -e -p -t -ms ms.ms >ms.pdf

I should have put a ".ps" extension on that.

> Doesn't run the build's _groff_, but whatever is in $PATH.
>
> The "canonical" way to evaluate a _groff_ you've just built, but not
> installed--and you haven't cross-compiled it--is to run the "test-groff"
> script.

I have installed it:

  ~/ % command -v groff
  /home/mojo/.local/bin/groff
  
The only groff related environment variable I have is:

  ~/ % env | grep -i groff
  GROFF_FONT_PATH=/home/mojo/.groff/fonts

> $ ASAN_OPTIONS="detect_leaks=0" ./test-groff -e -p -t -ms doc/ms.ms | okular

Yes, that also works for me. Strange.

Deri: I tried your command and it still fails.

Regards,
Morten
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.