From owner-freebsd-bugs Tue Jan 18 13:10: 4 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 80B94150FA for ; Tue, 18 Jan 2000 13:10:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id NAA24473; Tue, 18 Jan 2000 13:10:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 18 Jan 2000 13:10:03 -0800 (PST) Message-Id: <200001182110.NAA24473@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Archie Cobbs Subject: Re: bin/15929 [patch] clarify manpage for printf(1) Reply-To: Archie Cobbs Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/15929; it has been noted by GNATS. From: Archie Cobbs To: dhagan@cs.vt.edu (Daniel Hagan) Cc: archie@whistle.com (Archie Cobbs), freebsd-gnats-submit@freebsd.org Subject: Re: bin/15929 [patch] clarify manpage for printf(1) Date: Tue, 18 Jan 2000 13:01:05 -0800 (PST) Daniel Hagan writes: > > Looks great, thanks. .. but why "\e000" and not "\000" ? > > Well, I'm not familiar with man-page source formats (Troff?), but that's > what it appears to take to make a \000 appear in the output. For > reference, refer to lines 90-106 where the ANSI escape sequences are > listed. \000 resulted in \00 when I tried it. Ah, of course.. my ignorance :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message