* zsh completions
@ 2015-05-11 17:56 Kannan Varadhan
0 siblings, 0 replies; only message in thread
From: Kannan Varadhan @ 2015-05-11 17:56 UTC (permalink / raw)
To: zsh-users
[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]
I am seeing a couple of stumpers (for me) on zsh completions. Wanted to first reset the path to vanilla zsh. Then unlash and load complaint.
Last login: Mon May 11 10:47:08 on ttys008
/usr/share/zsh/site-functions /usr/share/zsh/5.0.5/functions
/Users/kvaradha/.rc/zshell/.zshrc:21: write error
~ 1% fpath=( /usr/share/zsh/site-functions /usr/share/zsh/5.0.5/functions )
~ 2% unhash -f compinit 10:47:37
~ 3% autoload -U compinit 10:47:41
~ 4% compinit 10:47:45
zsh: compinit: function not defined by file
~ 5% 10:47:47
It complains about one specific function, but I can’t tell which one, given a large number get autoloaded here..
~ 5% 10:47:49
~ 5% unhash -f compinit 10:47:49
~ 6% autoload -U compinit 10:47:54
~ 7% compinit 2>&- 10:47:56
zsh: write error
~ 8% 10:48:02
If I try to ignore the issue by closing stderr, I get this write error.
Now the stumper, this error only comes on after compinit has actually finished executing.
By this, I mean that the tail end of my compinit file is:
if [[ ${_i_line[2]} = expand-or-complete ]] &&
zstyle -a ':completion:' completer _i_line &&
(( ${_i_line[(i)_expand]} <= ${#_i_line} )); then
bindkey '^i' complete-word
fi
unfunction compinit compaudit
autoload -Uz compinit compaudit
return 0
and the error shows up after compinit has returned.
Puzzled,
Kannan
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-05-11 18:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-11 17:56 zsh completions Kannan Varadhan
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).