From: Phil Pennock <Phil.Pennock@globnix.org>
To: zsh-users@sunsite.dk
Subject: Re: Problems with modules and zsh 4.0.4
Date: Tue, 30 Oct 2001 15:25:51 +0100 [thread overview]
Message-ID: <20011030152551.A5818@globnix.org> (raw)
In-Reply-To: <20011030145042.A20640@greux.loria.fr>; from vincent@vinc17.org on Tue, Oct 30, 2001 at 02:50:42PM +0100
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On 2001-10-30 at 14:50 +0100, Vincent Lefevre wrote:
> But when I rlog to this machine, I get errors like:
>
> /users/spaces/lefevre/.zshrc:54: failed to load module: zsh/rlimits
> /users/spaces/lefevre/.zshrc:limit:54: autoload failed
> /users/spaces/lefevre/.zshrc:104: failed to load module: zsh/parameter
> /users/spaces/lefevre/.zshrc:305: failed to load module: zsh/zle
> /users/spaces/lefevre/.zshrc:bindkey:305: autoload failed
> /users/spaces/lefevre/.zshrc:306: command not found: bindkey
> /users/spaces/lefevre/.zshrc:307: command not found: bindkey
> [...]
>
> However, if I exec $SHELL after rlogging, I no longer get such
> problems. With zsh 4.0.2, there were no problems at all.
What happens if you add this:
typeset -m ZSH*
typeset module_path
before the first autoload?
Ie, what does it show for ZSH_VERSION at that point? What's the
module_path?
It sounds as though you're trying to load the old versions of the
modules; then, later, the paths are changed and with the exec, the
correct modules can be found.
--
I AM THE DEFENDER OF THE SOMETIMES-INEFFICIENT.
FEAR MY CAREFULLY WORDED AND REASONED WRATH.
- Chris Bellomy
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2001-10-30 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 13:50 Vincent Lefevre
2001-10-30 14:25 ` Phil Pennock [this message]
2001-10-30 17:40 ` Vincent Lefevre
2001-10-30 17:56 ` Vincent Lefevre
2001-10-30 18:04 ` Vincent Lefevre
2001-10-31 7:39 ` Borsenkow Andrej
2001-10-31 13:43 Raúl Núñez de Arenas Coronado
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=20011030152551.A5818@globnix.org \
--to=phil.pennock@globnix.org \
--cc=zsh-users@sunsite.dk \
/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).