From: TJ Luoma <luomat@gmail.com>
To: zsh-users@zsh.org
Subject: compinit causes completion to fail?
Date: Sun, 29 Apr 2012 01:21:20 -0400 [thread overview]
Message-ID: <E5557D87279D4F42B645D0604939B2C8@gmail.com> (raw)
I split my .zshenv and .zshrc into several smaller files which are sourced separately, and now I've broken completion :-/
If I include these two lines in my zshenv file[1]:
autoload -U compinit
compinit
then completion fails with this message:
_complete:117: command not found: _normal
and a ~/.zcompdump file is created [2]
but if I comment out those two lines:
#autoload -U compinit
#compinit
then completion seems to work OK.
HOWEVER, if I remove my ~/.zshenv and all related ~/.z* files, and then use 'autoload -U compinit' and 'compinit' then it works fine, and the 'zcompdump' file looks better [4], which further solidifies my belief that the problem here is something I've done in my .zshenv files… but what?
Did I fail to load something before turning on compinit, or did I set something too early? Bindkeys, perhaps?
If you look at the 'zcompdump' file [2], specifically at line 117, it says:
bindkey '^[g" get-lin'
that looks wrong to me. In fact, ALL of the bindkey lines look like they have lost the last character.
This started immediately after I split my ~/.zshenv file into several different files. You can see them all here [3]. This is using 4.3.11 on Mac OS X 10.7.3.
I have no idea what I've done here, but I'd appreciate any help.
TjL
[1]
https://www.dropbox.com/sh/7t1jagj5clkz0ci/_nzmp1eO9b/interactive/completion.sh
[2]
http://dl.dropbox.com/u/18414/tmp/zcompdump.txt
[3]
https://www.dropbox.com/sh/7t1jagj5clkz0ci/28xgQ85Mye
[4]
http://dl.dropbox.com/u/18414/tmp/zcompdump2.txt
next reply other threads:[~2012-04-29 5:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 5:21 TJ Luoma [this message]
2012-04-29 6:57 ` TJ Luoma
2012-04-29 18:29 ` Peter Stephenson
2012-04-30 0:24 ` Bart Schaefer
2012-04-30 5:04 ` TJ Luoma
2012-04-30 14:37 ` Bart Schaefer
2012-04-30 14:50 ` TJ Luoma
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=E5557D87279D4F42B645D0604939B2C8@gmail.com \
--to=luomat@gmail.com \
--cc=zsh-users@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).