From: Karel Balej <karelb@gimli.ms.mff.cuni.cz>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: man completion
Date: Sat, 21 May 2022 14:57:31 +0200 [thread overview]
Message-ID: <20220521125731.fexcrwbv7wabrod7@imladris> (raw)
In-Reply-To: <CAH+w=7Zb5Mc=dLw0EdHbHfi4OZRx=gbBH==6chO5FXj38wCK8w@mail.gmail.com>
Thank you for looking into this.
Inspired by your messages, I have been able to solve my problem. Just to
clarify, my issue was not that zsh would not pick up changes made to
MANPATH after the shell is started. I set MANPATH in /etc/profile which
is read by zsh and I was confused that it was not being appended to the
standard paths even though it started with a colon. Turns out the
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.
> 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).
The manual page does not mention that it should be combined in any way -
it only says _override_.
> 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.
[1] https://www.ibm.com/docs/en/aix/7.2?topic=m-man-command
Regards,
Karel
next prev parent reply other threads:[~2022-05-21 12:58 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 [this message]
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=20220521125731.fexcrwbv7wabrod7@imladris \
--to=karelb@gimli.ms.mff.cuni.cz \
--cc=schaefer@brasslantern.com \
--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).