[tex-live] display issue with "tlmgr help" ??

[Mojca Miklavec]

On 20 September 2017 at 17:07, George N. White III wrote:
> On 11 September 2017 at 16:22, Zdenek Wagner wrote:
>
>> I can confirm that perldoc perldoc behaves strangely om Mac but perldoc
>> -oman perldoc works. I have perl in /opt/local/bin/perl but port info perl
>> complains that perl does not exist. I do not remember how it was installed.

You probably have "perl5 +perl5_24" installed (which in turn installed
perl5.24).

You can check that with
    port provides /opt/local/bin/perl


> Apple provides (obsolete) /usr/bin/groff (version 1.19.2 on El Capitan) with
> the Xcode command-line tools.    There are 3 modules that perldoc can use to
> format terminal output:
>
> Pod::Perldoc::ToTerm (perldoc -oterm) , gives "1NAME1" output on macOS.
> This is the default on linux, macports, and Msys2 (Windows)
> Pod::Perldoc::ToMan (perldoc -oman -- requires groff, adds man-style
> headers)  used by Apple's perldoc
> Pod::Perldoc::ToText (perldoc -otext or perldoc -t), default for Windows
>
> I have no idea where the default behaviour is configured.  Macports should
> follow Xcode and make "-oman" the default.  Apple uses a number of
> outdated GNU tools to avoid GPL3, so I don't expect Unicode support will
> appear in Apple's groff.

If someone can provide me clear instructions what needs to be done in
MacPorts to make the man page work out of the box, I can probably fix
it. I remember some problems, but it wasn't anoying enough to dive
into it and figure out how to fix it. (I forgot my computer at home,
so I cannot test anything for a couple of days, but I can look later.)
The GPL3 licence is not a problem from the MacPorts point of view (it
might only be a problem if you wanted it to work out of the box on a
clean mac without a package manager).

Mojca