4.0.1-pre-4

4.0.1-pre-4

[Matthew Landis]

I apologize if this isn't a suitable question to ask here, but I spent five
hours yesterday looking at the documentation and webpages and was unable to
figure out what might be my problem.  I was running 3.1.9-dev-8, and it
worked fine.  I installed 4.0.1-pre-4 yesterday and couldn't get tab
completion to work.
When I run compinit, it seems to write its code to stdout and not do much
else.  .zcompdump is the following after I run compinit:
--------------
#files: 372
_comps=(
)
_services=(
)

_patcomps=(
)

_postpatcomps=(
)

_compautos=(
)


autoload -U
--------------
In addition, the * and ? wildcards do not work.  If I do a "ls *" it prints
a "ls: : No such file or directory" for each file that * would match.  The ?
wildcard just gives "no matches found" in all cases that I tried.
I tried renaming all of the .zsh and /etc/zsh files and running compinstall
on the bare configuration to no avail.
As far as I can tell by reading the docs, my fpath is set correctly.  I used
the default directories when configuring, and fpath is
"/usr/local/share/zsh/site-functions
/usr/local/share/zsh/4.0.1-pre-4/functions".  The latter directory contains
the completion functions.  If I bind tab to something other than
complete-word and then run compinit, tab doesn't get re-bound to
complete-word.  This makes me think that compinit isn't being run at all,
but the .zcompdump file is being written to, so I'm not quite sure what's
going on.
I'd appreciate any help anyone can offer, and I apologize if this is the not
the correct place to ask such questions.

Matt

Re: 4.0.1-pre-4

[Bart Schaefer]

On May 15,  8:06am, Matthew Landis wrote:
} Subject: 4.0.1-pre-4
}
} I apologize if this isn't a suitable question to ask here

No, this is exactly the right place.

} I installed 4.0.1-pre-4 yesterday and couldn't get tab completion to work.

First question:  Did "make check" work when you ran it in the build
directory?  (Or did you install prepackaged binaries from somewhere?)

(Note that you must "make" before "make check", the check target does
not rebuild the binary.)

What operating system and compiler do you have?

I'm going to jump ahead a bit:

} --------------
} In addition, the * and ? wildcards do not work.  If I do a "ls *" it prints
} a "ls: : No such file or directory" for each file that * would match.  The ?
} wildcard just gives "no matches found" in all cases that I tried.

Assuming you mean that wildcards don't work anywhere, even when you are
not attempting completion, then something is very seriously wrong with
your zsh build.  Failure of file globbing would explain most of the rest
of the problems you describe.  Please try rebuilding from scratch --
remove your entire old build tree and unpack the tar file again -- and
if the problem persists send a description of your operating system and
OS vendor, your compiler, the arguments you gave to "configure", etc. to
<zsh-workers@sunsite.dk>.

If that is not the problem, then:

} When I run compinit, it seems to write its code to stdout

What does "write its code to stdout" mean?  Do you actually see output of
some kind on your terminal?

} .zcompdump is the following after I run compinit:
} --------------
} #files: 372
} _comps=(
} )
} _services=(
} )
} 
} _patcomps=(
} )
} 
} _postpatcomps=(
} )
} 
} _compautos=(
} )
} 
} 
} autoload -U

What do you see if you run the command "compaudit"?

The above is exactly what I get from running "compinit -i" when NONE of
the completion directories is considered to be secure by compaudit.  If
compaudit complains, you probably either want to fix the permissions on
those directories, or else use "compinit -u".

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net