From: Oliver Kiddle <opk@u.genie.co.uk>
To: Zsh workers <zsh-workers@sunsite.auc.dk>
Cc: Adam Spiers <adam@spiers.net>
Subject: PATCH: Re: _man copes with : delimited manpath
Date: Wed, 06 Oct 1999 17:22:10 +0100 [thread overview]
Message-ID: <37FB7732.77D9B5EA@u.genie.co.uk> (raw)
In-Reply-To: <19990927141724.B10336@thelonious.new.ox.ac.uk>
Adam Spiers wrote:
> On my system, `manpath' generates colon-delimited paths, rather than
> space-delimited ones. This patch solves that problem. It also fixes
> what I think is a typo, but someone should check this.
Sorry, I wasn't thinking properly when I wrote it - all manpath commands I can find return a colon delimited string.
I prefered the more succinct way it was done so I'd suggest the following patch. An alternative would be to assign to MANPATH instead of manpath.
Oliver Kiddle
*** Completion/User/_man.bak Wed Oct 6 17:09:43 1999
--- Completion/User/_man Wed Oct 6 17:09:58 1999
***************
*** 14,25 ****
approx="(#a${_comp_correct})"
fi
! (( $#manpath )) || manpath=$(manpath 2>/dev/null) ||
manpath=( /usr/man(-/N) /(opt|usr)/(dt|share|X11R6|local)/(cat|)man(-/N) )
# `sman' is the SGML manual directory for Solaris 7.
! if [[ $words[2] = (<->*|ln) ]]; then
rep=(
$manpath/(sman|man|cat)${words[2]}/${~approx}$PREFIX${~star}$SUFFIX.<->*(N:t) )
else
--- 14,25 ----
approx="(#a${_comp_correct})"
fi
! (( $#manpath )) || manpath=( ${(s.:.)$(manpath 2>/dev/null)} ) ||
manpath=( /usr/man(-/N) /(opt|usr)/(dt|share|X11R6|local)/(cat|)man(-/N) )
# `sman' is the SGML manual directory for Solaris 7.
! if [[ $words[2] = (<->*|l|n) ]]; then
rep=(
$manpath/(sman|man|cat)${words[2]}/${~approx}$PREFIX${~star}$SUFFIX.<->*(N:t) )
else
next prev parent reply other threads:[~1999-10-06 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-27 13:17 PATCH: " Adam Spiers
1999-09-27 13:44 ` Peter Stephenson
1999-09-28 9:36 ` Tanaka Akira
1999-10-06 16:22 ` Oliver Kiddle [this message]
1999-10-06 17:24 ` PATCH: " Adam Spiers
1999-10-06 17:35 ` Adam Spiers
1999-10-07 8:43 ` Oliver Kiddle
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=37FB7732.77D9B5EA@u.genie.co.uk \
--to=opk@u.genie.co.uk \
--cc=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.dk \
/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).