Re: Removing the manpage requirement for GUI programs?
- To: email@example.com
- 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.firstname.lastname@example.org>
- In-reply-to: <ekpnb-3zRemail@example.com>
- References: <eiAmK-51Qfirstname.lastname@example.org> <eiAPM-5zYemail@example.com> <eiB98-6cXfirstname.lastname@example.org> <eiEql-2sJemail@example.com> <eiEA2-2FVfirstname.lastname@example.org> <eiFmq-3QDemail@example.com> <ek1kS-1Glfirstname.lastname@example.org> <ek4Vs-76Femail@example.com> <ekfxx-5WSfirstname.lastname@example.org> <ekhSG-QGemail@example.com> <ekpnb-3zRfirstname.lastname@example.org>
On 04/03/10 20:00, Yves-Alexis Perez wrote:
> > Josselin Mouette <email@example.com> 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.