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: Sat, 21 May 2022 13:22:57 -0700	[thread overview]
Message-ID: <CAH+w=7ZBvabbwWh07151ZgGKH4SNW1NChvLP2gVs6wA2hM4bMg@mail.gmail.com> (raw)
In-Reply-To: <20220521125731.fexcrwbv7wabrod7@imladris>

On Sat, May 21, 2022 at 5:57 AM Karel Balej <karelb@gimli.ms.mff.cuni.cz> wrote:
>
> problem was that I was using mandoc instead of man-db as the man
> provider, which however does not provide the manpath command.
>
> This is probably still a bug though, as the comment in _man claims that
> the function assumes either man-db or mandoc is used on Linux.

That really applies only to the structure of the tree and files it
looks for within the path; we don't attempt to reproduce the
functionality of `manpath` itself.  Is there any manpath equivalent
for mandoc?

> > Third, what additional locations should be searched on AIX when -m is
> > not present?  (And does anyone care?)
>
> Judging by the manual [1], probably just the /usr/share/man directory
> structure.

Thanks.


  reply	other threads:[~2022-05-21 20:24 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
2022-05-21 12:57       ` Karel Balej
2022-05-21 20:22         ` Bart Schaefer [this message]
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=7ZBvabbwWh07151ZgGKH4SNW1NChvLP2gVs6wA2hM4bMg@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).