Re: Removing the manpage requirement for GUI programs?
- To: firstname.lastname@example.org
- Subject: Re: Removing the manpage requirement for GUI programs?
- From: Roger Lynn <Roger@rilynn.me.uk>
- Date: Thu, 04 Mar 2010 22:51:15 +0000
- Message-id: <[🔎] 4B903963.email@example.com>
- In-reply-to: <ekpnb-3zRfirstname.lastname@example.org>
- References: <eiAmK-51Qemail@example.com> <eiAPM-5zYfirstname.lastname@example.org> <eiB98-6cXemail@example.com> <eiEql-2sJfirstname.lastname@example.org> <eiEA2-2FVemail@example.com> <eiFmq-3QDfirstname.lastname@example.org> <ek1kS-1Glemail@example.com> <ek4Vs-76Ffirstname.lastname@example.org> <ekfxx-5WSemail@example.com> <ekhSG-QGfirstname.lastname@example.org> <ekpnb-3zRemail@example.com>
On 04/03/10 20:00, Yves-Alexis Perez wrote:
> > Josselin Mouette <firstname.lastname@example.org> writes:
> > > Letting alone policy issues: what do you propose, *concretely* to
> > > improve the situation?
A man page containing a *brief* (one or two lines) description of what
the program does and pointers to further more comprehensive
documentation would be vastly better than no man page at all.
> My upstream position is exactly what started the thread: no need to have
> duplicate information between --help and manpage, --help strings are
> easily translatable (and translated), and they are more likely to be up
> to date.
And where is the --help option described? Many programs don't provide it
at all, and as has already been said there are many different switches
used to access the help amongst those that do.