Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

man completion hindered if MANPATH is set #160

Closed
veselov opened this issue Aug 31, 2017 · 1 comment
Closed

man completion hindered if MANPATH is set #160

veselov opened this issue Aug 31, 2017 · 1 comment

Comments

@veselov
Copy link
Contributor

veselov commented Aug 31, 2017

Hi.

I actually came to this through TACC/Lmod#191
The are packages that modify manpath, but leave an empty colon, which indicates to man that default manpath should be injected at that location.

The man autocompleter uses $MANPATH, and only invokes man -w if $MANPATH was empty. IMHO, it should call man -w. I don't see a situation where the value of $MANPATH individually should supercede.

To reproduce this problem, set your $MANPATH to :xxx, you would see that man pages still open up, but autocompleter can not suggest a single man page.
@scop scop closed this as completed in e6a4715 Sep 27, 2017
@scop
Copy link
Owner

scop commented Sep 27, 2017

Related test cases in 3b2fd04

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@scop @veselov