From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: texlive-bin profile script corrupts MANPATH
Date: Sat, 08 Oct 2022 01:35:35 +0200 [thread overview]
Message-ID: <20221007233535.75kfl9r0LeDvxToCyDdjGb39UFmRtLPOmjWhmMKGmEI@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: 506 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/39797#issuecomment-1272160714
Comment:
The `man` command definitely works even when the completions fail, but I didn't think the `mdocml` manual page was particularly clear. Its description of MANPATH made me believe it might abandon defaults or the configuration file when the environment variable was set.
I'll test the zsh fix and, if that solves the completion problem, we can merge the patch.
next prev parent reply other threads:[~2022-10-07 23:35 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 [this message]
2022-10-08 0:27 ` [ISSUE] [CLOSED] " ahesford
2022-10-08 0:27 ` ahesford
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=20221007233535.75kfl9r0LeDvxToCyDdjGb39UFmRtLPOmjWhmMKGmEI@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).