From: Danek Duvall <duvall@comfychair.org>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: _man completion update for Solaris
Date: Tue, 6 Sep 2016 18:11:50 -0700 [thread overview]
Message-ID: <20160907011150.GB24696@lorien.comfychair.org> (raw)
In-Reply-To: <20160906224508.GB4800@fujitsu.shahaf.local2>
On Tue, Sep 06, 2016 at 10:45:08PM +0000, Daniel Shahaf wrote:
> Danek Duvall wrote on Tue, Sep 06, 2016 at 11:06:14 -0700:
> > After finally looking at Daniel's _man changes, I saw that there were a
> > couple of small (pre-existing) issues on Solaris.
>
> Thanks for the review.
>
> > Namely: the -s option can take a comma-separated list of sections; and
> > the man-index directory gets thrown into the mix when it shouldn't.
> > This patch takes care of those two things.
>
> Thanks. The patch looks good to me. I'll push it tomorrow (not right
> now to give others a chance to respond).
Great, thanks.
> > I don't know if the comma/colon section separation should just be generic
> > -- it's safe to do on Solaris, since although we don't recognize the
> > separator, we don't have any sections that have colons in them -- but I
> > don't know if it's compatible with the third if clause there.
>
> "Third if clause" refers to what? If you mean the 'else' branch just
> below the context of the first hunk, then on my system «man 7,8 foo»
> looks for a section literally called "man7,8" whereas the same with -S
> looks in the "man7" and "man8" sections, so at least on my system the
> 'else" branch shouldn't s/,/|/. (My system runs Debian stable.)
"elif (( CURRENT > 2 ))", but the behavior you describe is the one I was
wondering about.
Thanks,
Danek
prev parent reply other threads:[~2016-09-07 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 18:06 Danek Duvall
2016-09-06 22:45 ` Daniel Shahaf
2016-09-07 1:11 ` Danek Duvall [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=20160907011150.GB24696@lorien.comfychair.org \
--to=duvall@comfychair.org \
--cc=d.s@daniel.shahaf.name \
--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).