From owner-freebsd-standards@FreeBSD.ORG Sun Feb 8 22:50:22 2004 Return-Path: Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEE8316A4D0 for ; Sun, 8 Feb 2004 22:50:22 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B34D343D2F for ; Sun, 8 Feb 2004 22:50:22 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i196oMbv057147 for ; Sun, 8 Feb 2004 22:50:22 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i196oMBp057146; Sun, 8 Feb 2004 22:50:22 -0800 (PST) (envelope-from gnats) Date: Sun, 8 Feb 2004 22:50:22 -0800 (PST) Message-Id: <200402090650.i196oMBp057146@freefall.freebsd.org> To: freebsd-standards@FreeBSD.org From: Wartan Hachaturow Subject: Re: standards/61934: [PATCH] FreeBSD's mailx not completely SUSv3-compliant X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Wartan Hachaturow List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2004 06:50:23 -0000 The following reply was made to PR standards/61934; it has been noted by GNATS. From: Wartan Hachaturow To: Mike Heffner Cc: Wartan Hachaturow , FreeBSD-gnats-submit@FreeBSD.org Subject: Re: standards/61934: [PATCH] FreeBSD's mailx not completely SUSv3-compliant Date: Mon, 9 Feb 2004 09:37:35 +0300 On Mon, Feb 09, 2004 at 12:59:59AM -0500, Mike Heffner wrote: > I've done a quick first pass, comments are inlined. Okay, thanks for looking at this :) I'll fix the issues you're pointed at, and submit a new version of the patch. > checkmail and use it instead for the -e option? Also, the fprintf that > displays "No mail for ..." should not be printed when using the -e option. > SuSv3 states that when using the -e option, nothing should be printed. Well, I've interpreted the phrase "The mailx utility shall write nothing and exit with a successful return code if there is mail to read" like that "one should not print anything in "there is mail" case". Of course, since most prospective use of -e is in scripts, printing in "no mail" case is, perhaps, futile :) -- Regards, Wartan. "Be different: conform."