public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: john doe <johndoe65534@mail.com>
To: cygwin@cygwin.com
Subject: Re: How to Setup Multiple System Distro Manpages
Date: Sun, 15 Jul 2018 15:40:00 -0000	[thread overview]
Message-ID: <c33f508d-cec0-0ae9-936a-9751d26e1e86@mail.com> (raw)
In-Reply-To: <e85d959b-289a-106b-b5e5-6a4a4974fccf@SystematicSw.ab.ca>

On 7/15/2018 9:21 AM, Brian Inglis wrote:
> On 2018-07-15 00:39, john doe wrote:
>> On 7/14/2018 10:50 PM, Brian Inglis wrote:
>>> I've installed a few WSL distros for comparison and downloaded a bunch of other
>>> manpage sets and unpacked them:
>>> $ l /proc/cygdrive/c/usr/local/share/man/
>>> cat1/          debian@                      man1p/  mann/           SunOS-5.10/
>>> cat3/          Debian-8.1.0/                man2/   netbsd@         suse@
>>> cat5/          freebsd@                     man3/   NetBSD-7.1/     SuSE-11.3/
>>> cat7/          FreeBSD-12-current/          man3p/  openbsd@        ubuntu@
>>> cat8/          FreeBSD-ports-11.1-RELEASE/  man4/   OpenBSD-6.2/    x@
>>> centos@        hpux@                        man5/   ports@          X11R7.4/
>>> CentOS-7.1/    HP-UX-11.22/                 man6/   redhat@
>>> darwin@        man0p/                       man7/   RedHat-9-i386/
>>> Darwin-7.0.1/  man1/                        man8/   solaris@
>>> but despite reading docs, adding links and changing configs, I'm unable to get
>>> man/-db to access these with or without the -m system switch.
>>> I know I must be missing some essential point, but searching has not come up
>>> with anything to help me fix this.
>>> Has anyone here set this up and can suggest an approach that will work?
>> In addition to the other answers; maybe exporting those directories in the
>> 'PATH' env variable...
> 
> I already tried listing them all at the end of man-db.conf and MANPATH.
> 

I was talking about the env 'PATH' var and not 'MANPATH' but that does 
not make any difference. :)

 From the test I've done and using:

https://www.cyberciti.biz/faq/linux-unix-creating-a-manpage/

$ cat ${HOME}/try/mann/bogus.n
.\" Manpage for bogus.
.\" Contact vivek@nixcraft.net.in to correct errors or typos.
.TH man 8 "06 May 2010" "1.0" "bogus man page"
.SH NAME
bogus \- create a new LDAP user
.SH SYNOPSIS
bogus [USERNAME]
.SH DESCRIPTION
bogus is high level shell program for adding users to LDAP server.  On 
Debian, administrators should usually use bogus.debian(8) instead.
.SH OPTIONS
The bogus does not take any options. However, you can supply username.
.SH SEE ALSO
bogus(8), passwd(5), bogus.debian(8)
.SH BUGS
No known bugs.
.SH AUTHOR
Vivek Gite (vivek@nixcraft.net.in)

$ man --manpath=${HOME}/try bogus
man(8) 
             bogus man page 
                                  man(8)

NAME
        bogus - create a new LDAP user

SYNOPSIS
        bogus [USERNAME]

DESCRIPTION
        bogus is high level shell program for adding users to LDAP 
server.  On Debian, administrators should usually use bogus.debian(8) 
instead.

OPTIONS
        The bogus does not take any options. However, you can supply 
username.

SEE ALSO
        bogus(8), passwd(5), bogus.debian(8)

BUGS
        No known bugs.

AUTHOR
        Vivek Gite (vivek@nixcraft.net.in)

1.0 
               06 May 2010 
                                  man(8)

HTH

-- 
John Doe

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-07-15 12:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-15  4:26 Brian Inglis
2018-07-15  4:32 ` Jack
2018-07-15  6:39   ` Brian Inglis
2018-07-15  7:19     ` Thomas Wolff
2018-07-15  6:49 ` Wayne Davison
2018-07-15 12:19   ` Brian Inglis
2018-07-15  7:21 ` john doe
2018-07-15 13:23   ` Brian Inglis
2018-07-15 15:40     ` john doe [this message]
2018-07-15 17:23       ` Thomas Wolff

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=c33f508d-cec0-0ae9-936a-9751d26e1e86@mail.com \
    --to=johndoe65534@mail.com \
    --cc=cygwin@cygwin.com \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).