[haiku] Re: Documenting your package
- From: "Thomas Mueller" <mueller6723@xxxxxxx>
- To: haiku@xxxxxxxxxxxxx
- Date: Tue, 05 Apr 2016 08:27:11 +0000
man and info are not so Haiku friendly, though. You have to use the ***x
command-line
programs to read them, so they do need their own hierarchy. (I wonder if it
would be
worth giving them mimetypes, and preferred apps, so a user *could* click on
the file
to read it? You could even then have links to those pages from the main doc
folder for
that app [I actually long ago set up a xicon script that you can drop a man
file on to read].)
I guess I can live with .../documentation/packages as long it is a clear
standard, documented
somewhere.
-- Pete --
I believe you need "man" to read man pages, but reading an info page with
"info" is an awful nuisance, I always do something wrong and need q to escape.
I could read an info page better with "less" than with info!
KDE's Konqueror did a good job with info pages, at least in Linux Slackware
13.0. Otherwise, there is pinfo, which I find is not in haikuports.
pinfo is text mode with interface rather like Lynx web browser, much nicer than
the command-line "info".
Tom
Other related posts:
