Date: Sat, 13 Feb 1999 13:52:25 -0800 (PST) From: Mike Pritchard <mpp> To: fenner@parc.xerox.com (Bill Fenner) Cc: fenner@parc.xerox.com, 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: <199902132152.NAA22280@hub.freebsd.org> In-Reply-To: <199902132048.MAA15838@mango.parc.xerox.com> from Bill Fenner at "Feb 13, 99 12:48:54 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Fenner wrote: > In message <199902131953.LAA08961@hub.freebsd.org>you write: > >How about issuing a *roff error message when some "unknown" release > >is specified with the .Fx macro? > > That's fine for the people who are writing the man page, but pretty > much sucks for the people who are just trying to use the system > and come across a man page that won't format. I'd be happy to > create another set of macros that developers can opt to use. It doesn't have to be a fatal error. You should be able to issue a warning message and still have the manual page format correctly. When I was cleaning up the man pages way back when, there were a number of man pages that issued *roff warning errors, but still formatted more or less correctly. As long as the .Fx macro causes the correct text to be formatted in addtion to the warning message, things should be fine. When release time approaches, someone should format all of the manual pages and check for *roff errors and fix them before the release. -- 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?199902132152.NAA22280>