On Thu, May 8, 2014 at 2:38 PM, Werner LEMBERG wrote:
>
>> I suppose the solution is to note that the user should look in the
>> documentation for their installed version of groff, and ask
>> distributions of groff to document it (or reconsider having this
>> variable in the first place).
>
> Firs
> In dynamic programming we maintain a set of optimum partial solutions,
> each stored as a node in an acyclic directed graph. Edges of the graph
> indicate from which partial solution an extended partial solution was
> derived.
> Finally we end up with a set of complete solutions, pick the best on
> I suppose the solution is to note that the user should look in the
> documentation for their installed version of groff, and ask
> distributions of groff to document it (or reconsider having this
> variable in the first place).
First of all, you should submit a bug report to the affected GNU/Li
On Thu, May 8, 2014 at 12:01 PM, Werner LEMBERG wrote:
>> Could groff document it as a variable that doesn't do anything, or
>> could distributions of groff document it somehow?
>
> IMHO, the GNU/Linux distributions that have introduced this
> environment variable should also update the man page o
> [...] it seems that many distributions of groff have added another
> variable, GROFF_SGR, which is needed to turn these codes *on*.
>
> This is an issue with the standalone Info browser that is part of
> texinfo, which can pass through SGR codes when displaying man pages,
> but cannot display in
