Date: Thu, 16 Sep 2010 01:44:42 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: Juli Mallett <jmallett@FreeBSD.org> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn commit: r212374 - head/usr.bin/printf Message-ID: <20100916084442.GB21622@dragon.NUXI.org> In-Reply-To: <AANLkTi=1KXtmwVobbnk8vCkQKDN01RxWh8Q5ZZqzU0tq@mail.gmail.com> References: <201009091927.o89JReXm022426@svn.freebsd.org> <AANLkTi=1KXtmwVobbnk8vCkQKDN01RxWh8Q5ZZqzU0tq@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 09, 2010 at 12:51:11PM -0700, Juli Mallett wrote: > On Thu, Sep 9, 2010 at 12:27, David E. O'Brien <obrien@freebsd.org> wrote: > > Author: obrien > > Date: Thu Sep 9 19:27:40 2010 > > New Revision: 212374 > > URL: http://svn.freebsd.org/changeset/base/212374 > > > > Log: > > Note bug in trying to printf(1) things like: '-%s\n' "foo" > > Should we also add something like this note to every manual page for a > program that operates on files as command line arguments after options > w.r.t. operating on files whose names begin with '-'? No. Because most programs have a synopsis like: ls [-ABCFGHILPRSTUWZabcdfghiklmnopqrstuwx1] [-D format] [file ...] However, printf(1)'s is printf format [arguments ...] Which does not say it takes ANY command-line options. Thus why should one expect to have to trick out any command-line arguments "--" as one would with 'grep -- --i *.c'? Is a sentence or two a burden to the man page vs. saving someone the time I spent trying to figure out why printf(1) kept throwing up errors? -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100916084442.GB21622>