From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 31 Jul 2014 13:44:05 +0200 From: Carsten Kunze To: 9fans@9fans.net Message-ID: <1861291544.267528.1406807045858.JavaMail.ngmail@webmail08.arcor-online.net> In-Reply-To: <53da264f.hfcL8fli/GQKu747%plan9@utroff.org> References: <53da264f.hfcL8fli/GQKu747%plan9@utroff.org> <483379591.893098.1406560151883.JavaMail.ngmail@webmail13.arcor-online.net> <460597530.893702.1406563095699.JavaMail.ngmail@webmail13.arcor-online.net> <132966297.894580.1406566609131.JavaMail.ngmail@webmail13.arcor-online.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] troff documentation link broken Topicbox-Message-UUID: 0a021bb0-ead9-11e9-9d60-3106f5b1d025 > Please correct me if I'm wrong, but I don't think there's > any bug here : > > The .ul internal command draw an underline when possible, > and use italics when it's not possible. For example, on a > terminal without underlining capabilities, italics are used. > > .us is just an example of an handmade underlining > macro, which is not expected to be implemented in all the > macro sets. The whole paragraph does not make sense if .ul is used. Why defining .us and not using it. This is a typo. troff doesn't underline by itself. One way is to write a custom macro (as .us) or use ms macro's .UL. .ul only underlines in nroff. Cheers, Carsten