zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: incomplete sentence in manual
Date: Mon, 28 Sep 2015 18:30:16 -0700	[thread overview]
Message-ID: <150928183016.ZM29411@torch.brasslantern.com> (raw)
In-Reply-To: <20150928181235.GA4921@tarsus.local2>

On Sep 28,  6:12pm, Daniel Shahaf wrote:
} Subject: incomplete sentence in manual
}
} Commit 18d82a6c401758e8bd49fef9478168c68d7d2652 contains:
} 
}     @@ -170,7 +174,8 @@ pattern are loaded.
}      With the tt(-w) flag, the var(name)s are taken as names of files compiled
}      with the tt(zcompile) builtin, and all functions defined in them are
}     -marked for autoloading.
}     +marked for autoloading.  Note this does not otherwise change the search
}     +order for
}     
} Could the end of the sentence be committed too, please?

Oops.  I went looking for where $fpath processing was discussed in order to
decide whether it was OK to call it out here, and then got distracted with
other edits and never came back to that thought.

So either the entire fragment should be deleted (it's now covered by the
first paragraph under autoload which was added by that same commit), or
if you don't feel that's sufficient then:


diff --git a/Doc/Zsh/builtins.yo b/Doc/Zsh/builtins.yo
index 97c3370..691aaeb 100644
--- a/Doc/Zsh/builtins.yo
+++ b/Doc/Zsh/builtins.yo
@@ -175,7 +175,7 @@ pattern are loaded.
 With the tt(-w) flag, the var(name)s are taken as names of files compiled
 with the tt(zcompile) builtin, and all functions defined in them are
 marked for autoloading.  Note this does not otherwise change the search
-order for 
+order via tt(fpath) when the function is first called.
 
 The flags tt(-z) and tt(-k) mark the function to be autoloaded using the
 zsh or ksh style, as if the option tt(KSH_AUTOLOAD) were unset or were


I can go either way.


      reply	other threads:[~2015-09-29  1:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 18:12 Daniel Shahaf
2015-09-29  1:30 ` Bart Schaefer [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=150928183016.ZM29411@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).