From: Oliver Kiddle <opk@u.genie.co.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: _man only uses $manpath
Date: Fri, 17 Sep 1999 10:35:42 +0100 [thread overview]
Message-ID: <37E20B6E.EB76FC79@u.genie.co.uk> (raw)
In-Reply-To: <199909170723.JAA01955@beta.informatik.hu-berlin.de>
Sven Wischnowsky wrote:
> Andrej Borsenkow wrote:
> > On Thu, 16 Sep 1999, Adam Spiers wrote:
> > > Sounds like we need some way of intelligently figuring out a solution
> > > for both scenarios. Does `man -w' return an error of some sort on
> > > your system which we could test for?
> > Well, exit code != 0. I have no idea, how reliable it is (different
> > versions etc)
>
> Same here for Digital Unix. Maybe we should test $OSTYPE?
The only man I can find which does support -w or --path is the GNU one.
The exit code of != 0 seems fine on the systems I've looked at provided
stderr is redirected.
What are you trying to achieve with man -w - find a default manpath to
use if $manpath is unset? As far as I can tell man -w only gives you the
location of a specific man page which isn't entirely useful for finding
a default manpath as the default can (and often will) contain more than
one directory. The only way I know of finding the default manpath is by
running the man binary through strings. Maybe we could use a for loop to
guess possible man directories and check them.
Oliver Kiddle
next prev parent reply other threads:[~1999-09-17 9:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-17 7:23 Sven Wischnowsky
1999-09-17 9:35 ` Oliver Kiddle [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-17 9:45 Sven Wischnowsky
1999-09-17 11:22 ` Adam Spiers
1999-09-17 12:43 ` Oliver Kiddle
1999-09-17 12:54 ` Clint Adams
1999-09-17 13:04 ` Clint Adams
1999-09-16 15:54 Adam Spiers
1999-09-16 16:19 ` Andrej Borsenkow
1999-09-16 16:21 ` Adam Spiers
1999-09-16 16:26 ` Andrej Borsenkow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37E20B6E.EB76FC79@u.genie.co.uk \
--to=opk@u.genie.co.uk \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).