From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4504 invoked by alias); 5 Mar 2011 08:54:50 -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: 28860 Received: (qmail 26118 invoked from network); 5 Mar 2011 08:54:48 -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: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <110305005435.ZM14083@torch.brasslantern.com> Date: Sat, 05 Mar 2011 00:54:35 -0800 In-reply-to: <20110305003734.GA26518@redoubt.spodhuis.org> Comments: In reply to Phil Pennock "zcompile dir oddity with unmatched `" (Mar 4, 7:37pm) References: <20110305003734.GA26518@redoubt.spodhuis.org> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: zcompile dir oddity with unmatched ` MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Mar 4, 7:37pm, Phil Pennock wrote: } } % cd ~/bin } % mkdir N } % zcompile N Hang on a minute. The zcompile builtin doesn't accept directory names as arguments: schaefer<507> cd /tmp schaefer<508> mkdir N schaefer<509> zcompile N zcompile: can't read file: N So you must be using a function or script named zcompile which at some point calls "builtin zcompile"? Until we know what your wrapper is doing, I don't think we can be of that much help. } Something hinky; I don't have time to investigate further right now, so } throwing this out in case someone else has seen this and knows what } might be happening. Does your wrapper use "builtin zcompile -U"? If not, try that. If that solves it, it's a problem with an alias somewhere; that's the most likely source of zcompile errors. You noted that: } % for f in zsh-funcs/*; do print $f; cp $f N; zcompile N; done } [ 8 items go in, before a problem, which then disappears with the 9th } item; reappears with 23rd item, disappears again ] As soon as the problem occurs you should check (possibly in another shell) whether loading the previous (seemingly error-free) zwc file correctly defines all the compiled functions (e.g., look at the output of the "functions" command).