From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] texlive-bin profile script corrupts MANPATH
Date: Sat, 08 Oct 2022 02:27:33 +0200 [thread overview]
Message-ID: <20221008002733.idAWuoVNTT_wlr2oJ9Oad0OvI2jtZjT-0-kL2HMeGXE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39797@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]
Closed issue by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/39797
Description:
The additon of `MANPATH` to `/etc/profile.d/texlive.sh` in https://github.com/void-linux/void-packages/commit/37e10282c3e7af286bea3aabb7ad4445ccd7de77 breaks completions for `man` in `zsh`. Previously, `MANPATH` was not set in the environment, which means that `zsh` looks for completions in default locations and finds everything in `/usr/share/man`. However, the new behavior results in `MANPATH=:/opt/texlive/2022/texmf-dist/doc/man`, which means `zsh` will **only** search in the listed directory. Note, also, the leading `:` which results from failing to check whether `MANPATH` is empty before appending the TeXLive path.
I'm not sure what the right fix is, but I guess my prefence would be something like
```sh
[ -n "${MANPATH}" ] && MANPATH="${MANPATH}:/opt/texlive/2022/texmf-dist/doc/man"
```
This will leave `MANPATH` blank by default and leave TL out of the search path, but I suspect that it's generally preferrable to find the system manual pages via tab completion instead of only showing TL pages. The user can always opt into TL manpages by defining a non-zero `MANPATH` in, *e.g.*, `/etc/environment` or a preceding file in `/etc/profile.d`.
cc: @leahneukirchen @balejk
prev parent reply other threads:[~2022-10-08 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 20:24 [ISSUE] " ahesford
2022-10-07 21:27 ` balejk
2022-10-07 22:58 ` classabbyamp
2022-10-07 23:35 ` ahesford
2022-10-08 0:27 ` ahesford
2022-10-08 0:27 ` ahesford [this message]
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=20221008002733.idAWuoVNTT_wlr2oJ9Oad0OvI2jtZjT-0-kL2HMeGXE@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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).