From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: zsh-5.2-test-3
Date: Mon, 12 Dec 2016 09:02:30 -0800 [thread overview]
Message-ID: <584ED826.8030700@eastlink.ca> (raw)
In-Reply-To: <161212083740.ZM1095@torch.brasslantern.com>
On 12/12/2016 08:37 AM, Bart Schaefer wrote:
> On Dec 11, 5:04pm, Ray Andrews wrote:
> }
> } Yeah, did that now and it takes me to the right man page, but
> } doesn't search within it for the command
>
> Oh, one bit I overlooked -- if you're running zsh with $fpath pointing
> into the build tree, it will not find the help files without some more
> configuration -- the location is substituted into the run-help function
> definition by "make install".
>
> To run out of the build tree, you have to explicitly assign the HELPDIR
> parameter to point to the appropriate Doc/help subdirectory.
>
Sorry Bart I don't have any idea what you mean.
3 /aWorking 2$ echo $fpath
/usr/local/share/zsh/site-functions
/aWorking/zsh-5.2-test-3/share/zsh/site-functions
/aWorking/zsh-5.2-test-3/share/zsh/5.2-test-3/functions
... the first directory doesn't exist, the others are correct (based on
" --prefix= "), and why would I want $fpath pointing anywhere else?
Anyway, as yesterday, " $ run-help test " takes me to "zshbuiltins" and
that's what I want, no? Throw in Daniel's insights into better
searching, and it's pretty functional.
However " $ run-help zmv " finds nothing, tho it is there in 'zshall'
but just a single line.
next prev parent reply other threads:[~2016-12-12 17:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161206195028epcas2p3c53119ab37952571be3238cdf228d88f@epcas2p3.samsung.com>
2016-12-06 19:49 ` zsh-5.2-test-2 Peter Stephenson
2016-12-09 9:57 ` zsh-5.2-test-2 Peter Stephenson
2016-12-09 19:54 ` zsh-5.2-test-3 Peter Stephenson
2016-12-11 2:07 ` zsh-5.2-test-3 Ray Andrews
2016-12-11 3:46 ` zsh-5.2-test-3 Ray Andrews
2016-12-11 17:15 ` zsh-5.2-test-3 Peter Stephenson
2016-12-11 18:16 ` zsh-5.2-test-3 Ray Andrews
2016-12-11 19:23 ` zsh-5.2-test-3 Bart Schaefer
2016-12-11 20:19 ` zsh-5.2-test-3 Ray Andrews
2016-12-11 23:45 ` zsh-5.2-test-3 Bart Schaefer
2016-12-12 1:04 ` zsh-5.2-test-3 Ray Andrews
2016-12-12 16:37 ` zsh-5.2-test-3 Bart Schaefer
2016-12-12 17:02 ` Ray Andrews [this message]
2016-12-12 17:39 ` zsh-5.2-test-3 Bart Schaefer
2016-12-12 21:11 ` zsh-5.2-test-3 Ray Andrews
2016-12-12 22:28 ` zsh-5.2-test-3 Bart Schaefer
[not found] ` <584F1269.7060604__3570.10125085271$1481577154$gmane$org@eastlink.ca>
2016-12-12 23:35 ` zsh-5.2-test-3 Daniel Shahaf
2016-12-13 1:30 ` zsh-5.2-test-3 Ray Andrews
[not found] ` <584DF7A1.6010906__17132.6343705461$1481504750$gmane$org@eastlink.ca>
2016-12-12 8:37 ` zsh-5.2-test-3 Daniel Shahaf
2016-12-12 16:28 ` zsh-5.2-test-3 Ray Andrews
2016-12-12 17:14 ` zsh-5.2-test-3 Bart Schaefer
2016-12-12 20:08 ` zsh-5.2-test-3 Ray Andrews
[not found] ` <584DB4BA.4050802__43705.4374524907$1481487619$gmane$org@eastlink.ca>
2016-12-11 23:07 ` zsh-5.2-test-3 Daniel Shahaf
[not found] ` <584CB4EF.6070904__42420.2079572298$1481423945$gmane$org@eastlink.ca>
2016-12-11 3:09 ` zsh-5.2-test-3 Daniel Shahaf
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=584ED826.8030700@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@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).