Date: Thu, 9 Sep 2010 12:51:11 -0700 From: Juli Mallett <jmallett@FreeBSD.org> To: "David E. O'Brien" <obrien@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: <AANLkTi=1KXtmwVobbnk8vCkQKDN01RxWh8Q5ZZqzU0tq@mail.gmail.com> In-Reply-To: <201009091927.o89JReXm022426@svn.freebsd.org> References: <201009091927.o89JReXm022426@svn.freebsd.org>
index | next in thread | previous in thread | raw e-mail
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 '-'? It seems like if it's appropriate in individual manpages at all it's appropriate in all of them — it's one of the most frequently-asked questions by new Unix users that I've encountered. On the other hand, perhaps intro(1) or similar is more appropriate. Juli.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=1KXtmwVobbnk8vCkQKDN01RxWh8Q5ZZqzU0tq>