From owner-freebsd-bugs  Sun Nov 11  9: 0: 7 2001
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id C1D8237B41C
	for <freebsd-bugs@hub.freebsd.org>; Sun, 11 Nov 2001 09:00:01 -0800 (PST)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.11.4/8.11.4) id fABH01G06044;
	Sun, 11 Nov 2001 09:00:01 -0800 (PST)
	(envelope-from gnats)
Date: Sun, 11 Nov 2001 09:00:01 -0800 (PST)
Message-Id: <200111111700.fABH01G06044@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Giorgos Keramidas <charon@labs.gr>
Subject: Re: bin/31392: fmt(1) does format nroff source ...
Reply-To: Giorgos Keramidas <charon@labs.gr>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR bin/31392; it has been noted by GNATS.

From: Giorgos Keramidas <charon@labs.gr>
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Cc: freebsd-gnats-submit@FreeBSD.org, kurt@boolean.net
Subject: Re: bin/31392: fmt(1) does format nroff source ...
Date: Sun, 11 Nov 2001 18:51:43 +0200

 Kurt D. Zeilenga <Kurt@OpenLDAP.org> wrote:
 > At 07:11 PM 2001-11-10, charon@labs.gr wrote:
 > >
 > >The rewrite of fmt(1) at revision 1.12 -> 1.13 of fmt.c behaves differently,
 > >but this is not really a bug.
 >
 > I've been using fmt(1) to format [nt]roff files (such as man
 > pages) for 20 years, fmt has behaved in a certain behavior
 > manner.  While you can argue all you want about which behavior
 > is more 'correct' or more 'wrong', I argue that changing
 > historical behavior is plain 'wrong' a very good technical
 > reason.  Where one does have good reason to introduce new behavior,
 > it should be optional. Or, at least, the historical behavior
 > is be available as an option.
 
 I am not arguing for or against any of the two.  I've used fmt in
 SunOS systems a few years back, but I don't remember if it behaved the
 same way.  I just noted that this is definitely a change in behavior
 and a likely POLA violation.
 
 I'm already reading through the new fmt(1) code to see how easy it is
 to provide the old behavior.  Any patches, are welcome :)
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message