Re: .Fn _* issue

[Kristaps Dzonsons <kristaps@bsd.lv>]

>>>>   GNU nroff (groff) version 1.18.1
>>>>   nroff -mandoc foo.1 | hexdump -c
>>>>   _  \b   _   f  \b   f   l  \b   l   u  \b
>>>>
>>>>   mandoc foo.1 | hexdump -c
>>>>   _  \b   _   f  \b   f   l  \b   l   u  \b
>>>>
>>>>   GNU troff version 1.15
>>>>   nroff -mandoc foo.1 | hexdump -c
>>>>   _  \b   _   f  \b   f   l  \b   l   u  \b
>>>>
>>>>
>>> hmm, and you do not see the issue i describe? what else could it be?
>>> surely not my TERM setting if mandoc shows it one way and groff another.
>>>
>>> what else?
>> Jason,
>>
>> It could be groff acting upon TERM.  When I run this under a linux
>> terminal, for example, the underscores are colourised like the `Fa'
>> token (i.e., "underlined").  Do note that "_ \b _" is ambiguous: it
>> could either mean an underlined underscore or a bold underscore.
>>
>> (I ran the above in TERM=rxvt.)
>>
> 
> hmm. i use TERM=wsvt25. so do you think there is a bug in the term code,
> or it's something else?

There's nothing mandoc can do about it: the "_" character produces the
same escape sequence when it's underlined as when it's bold ("_\b_").  I
observe that, in this situation, the "underline" style has precedence
(by colouring on the "linux" terminal).
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv