From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18879 invoked by alias); 27 Feb 2011 22:40:12 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 28807 Received: (qmail 24911 invoked from network); 27 Feb 2011 22:40:09 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 Received-SPF: pass (ns1.primenet.com.au: SPF record at ntlworld.com designates 81.103.221.58 as permitted sender) Date: Sun, 27 Feb 2011 22:10:46 +0000 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: Doc bug: sched / set Message-ID: <20110227221046.6b16aab9@pws-pc.ntlworld.com> In-Reply-To: <110227125549.ZM4780@torch.brasslantern.com> References: <110227125549.ZM4780@torch.brasslantern.com> X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.0; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Cloudmark-Analysis: v=1.1 cv=R50lirqlHffDPPkwUlkuVa99MrvKdVWo//yz83qex8g= c=1 sm=0 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=NLZqzBF-AAAA:8 a=AskENxuRKRH0GkyIVNUA:9 a=DbafR2yiEgyjhJrEUewA:7 a=6TR2MgvTfsSTM124Bxr5PoJ2i-IA:4 a=CjuIK1q_8ugA:10 a=I6wTmPyJxzYA:10 a=_dQi-Dcv4p4A:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 On Sun, 27 Feb 2011 12:55:49 -0800 Bart Schaefer wrote: > The builtins.yo reference to the "sched" command got converted at some > point into a use of the module() macro. The problem is, that left some > stray text behind which got incorporated on the end of the description > of the "set" builtin: > > The tt(sched) builtin is not made available by default when the shell > starts in a mode emulating another shell. It can be made available > with the command `tt(zmodload -F zsh/sched b:sched)'. > > Several choices possible here: > > (1) Delete this text entirely. > (2) Move the text from the builtins.yo to mod_sched.yo. > (3) Create an xmodule() macro that accepts a third argument and pass the > text there, so it appears in the correct item() in builtins.yo I'd have thought (2) would be adequate. -- Peter Stephenson Web page now at http://homepage.ntlworld.com/p.w.stephenson/