zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Karel Balej <karelb@gimli.ms.mff.cuni.cz>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: man completion
Date: Mon, 16 May 2022 17:41:09 -0700	[thread overview]
Message-ID: <CAH+w=7Zb5Mc=dLw0EdHbHfi4OZRx=gbBH==6chO5FXj38wCK8w@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Yt84uC0PVNvjoXjh3apmYMgvXNYeSUdqPcg9vaZ4DEKA@mail.gmail.com>

On Mon, May 16, 2022 at 12:41 PM Bart Schaefer
<schaefer@brasslantern.com> wrote:
>
> Here's a patch that attempts to (1) skip the cache entirely if the -M
> option appears

Hm, my "man man" says of -M
> ... overrides the $MANPATH environment variable and causes option -m to be ignored.

Whereas the AIX help string in _man says
> '-m[only search paths specified by -M/MANPATH]'

And of course on linux/macos/dragonfly/freebsd -m means to search
manuals of other operating systems, whereas on netbsd/openbsd it means
to append to MANPATH.

The last of those seems to be the only alternative actually supported.

First question, if the argument to -M has leading/doubled/trailing
colons, is it supposed to be treated like $MANPATH with respect to
adding the system paths?  (It doesn't appear so, on Ubuntu 20 at
least).

Second, does anyone know where the manuals of other OSs would be found?

Third, what additional locations should be searched on AIX when -m is
not present?  (And does anyone care?)


  parent reply	other threads:[~2022-05-17  0:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 15:20 Karel Balej
2022-05-15 16:45 ` Bart Schaefer
2022-05-16 19:41   ` Bart Schaefer
2022-05-16 21:40     ` Mikael Magnusson
2022-05-17  0:41     ` Bart Schaefer [this message]
2022-05-21 12:57       ` Karel Balej
2022-05-21 20:22         ` Bart Schaefer
2022-05-22 16:00           ` Karel Balej
2022-05-22 21:26             ` Bart Schaefer
2022-05-23 12:28               ` Karel Balej

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='CAH+w=7Zb5Mc=dLw0EdHbHfi4OZRx=gbBH==6chO5FXj38wCK8w@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=karelb@gimli.ms.mff.cuni.cz \
    --cc=zsh-workers@zsh.org \
    /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).