Date: Sat, 13 Feb 1999 11:53:50 -0800 (PST) From: Mike Pritchard <mpp> To: fenner@parc.xerox.com (Bill Fenner) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, wosch@cs.tu-berlin.de, pst@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: Fx and Os macros (was: Re: [yokota@zodiac.mech.utsunomiya-u.ac.jp: .Fx and .Os macros in groff, FreeBSD]) Message-ID: <199902131953.LAA08961@hub.freebsd.org> In-Reply-To: <99Feb10.113323pst.177534@crevenia.parc.xerox.com> from Bill Fenner at "Feb 10, 99 11:33:20 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Fenner wrote: > After testing my macros some more, I'm sure they work. The only reason > to not commit them is because we think it's better to print an empty > string for unknown releases (like 2.2.2 was, before you fixed it, and > of course 3.1 and 4.0). I think it's a much better failure mode to allow > .Fx 1.2.3.4 to print "FreeBSD 1.2.3.4" than it is to allow ".Fx 4.0" > to print "". How about issuing a *roff error message when some "unknown" release is specified with the .Fx macro? That will serve as a reminder to update the macro, and hopefully identify man pages with bogus releases specified with the .Fx macro. Last time I did anything with all this, I found a number of man pages that referenced releases that never existed. -- Mike Pritchard mpp@FreeBSD.org "Go that way. Really fast. If something gets in your way, turn" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902131953.LAA08961>