Re: Removing the manpage requirement for GUI programs?
Yves-Alexis Perez wrote:
> On jeu., 2010-03-04 at 22:54 +1100, Ben Finney wrote:
> > Josselin Mouette <email@example.com> writes:
> > > Letting alone policy issues: what do you propose, *concretely* to
> > > improve the situation?
> > The situation is as it is: many commands lack proper manual pages. I
> > don't propose to change the existing approach for dealing with this:
> > file bug reports, work with upstream to have properly maintained
> > manpages, close the bug reports as fixed when that happens.
> 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.
What's the problem, to write a short manual page, that points to the
--help switch? All the maintainer would have to do is to provide the
intention of the command, point to the help/usage switch, relevant
commands and to locally installed documentation. Such a manual page
won't unlikely become outdated and it doesn't need much maintenance.
This goes for both: authors and maintainers. But it still provides the
necessary information to the user.
You need a dozen GROFF macros and 2 or 3 escapes. And this is a
burden to you guys? Really?
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01