Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Feb 2004 04:30:13 -0800 (PST)
From:      Wartan Hachaturow <wart@tepkom.ru>
To:        freebsd-standards@FreeBSD.org
Subject:   Re: standards/61934: [PATCH] FreeBSD's mailx not completely SUSv3-compliant
Message-ID:  <200402181230.i1ICUDCe059435@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR standards/61934; it has been noted by GNATS.

From: Wartan Hachaturow <wart@tepkom.ru>
To: Mike Heffner <mheffner@vt.edu>
Cc: FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: standards/61934: [PATCH] FreeBSD's mailx not completely	SUSv3-compliant
Date: Wed, 18 Feb 2004 15:18:56 +0300

 On Mon, Feb 09, 2004 at 12:59:59AM -0500, Mike Heffner wrote:
 
 > your modified setfile() should work in those cases as well. So, can you
 > modify setfile to return a more descriptive error code like in your
 > checkmail and use it instead for the -e option? Also, the fprintf that
 
 Well, if we're agreed on not printing "No mail for .." in -e case, then there's
 a problem with setfile usage, which prints that for other usage cases. Of 
 course, I can add an additional flag to arguments, but.. Isn't it clearer to 
 use another function? 
 There is also an option of splitting setfile() in smaller parts, but it isn't 
 pretty applicable here -- hardly any part of it could be used in other places,
 than check_mail().
 
 Your words are my command :)
 
 -- 
 Regards, Wartan.
 "Be different: conform."



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402181230.i1ICUDCe059435>