From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: zcompile dir oddity with unmatched `
Date: Sat, 05 Mar 2011 00:54:35 -0800 [thread overview]
Message-ID: <110305005435.ZM14083@torch.brasslantern.com> (raw)
In-Reply-To: <20110305003734.GA26518@redoubt.spodhuis.org>
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).
next prev parent reply other threads:[~2011-03-05 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 0:37 Phil Pennock
2011-03-05 8:54 ` Bart Schaefer [this message]
2011-03-05 22:16 ` Phil Pennock
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=110305005435.ZM14083@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).