Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
RE: Slow compdump on Vista - no .zcompdump created
- X-seq: zsh-users 12113
- From: "John Cooper" <John.Cooper@xxxxxxxxxx>
- To: "Peter Stephenson" <pws@xxxxxxx>, "Zsh Users" <zsh-users@xxxxxxxxxx>
- Subject: RE: Slow compdump on Vista - no .zcompdump created
- Date: Thu, 25 Oct 2007 12:12:59 +0100
- Cc: "John Cooper" <John.Cooper@xxxxxxxxxx>
- In-reply-to: <200710251044.l9PAi9Ag016224@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <DD74FBB8EE28D441903D56487861CD9D22719534@xxxxxxxxxxxxxxxxxxxxxx> <016801c8164c$301c5d70$90551850$@com> <DD74FBB8EE28D441903D56487861CD9D2271979B@xxxxxxxxxxxxxxxxxxxxxx> <018501c81658$6beebbc0$43cc3340$@com> <DD74FBB8EE28D441903D56487861CD9D2271A057@xxxxxxxxxxxxxxxxxxxxxx> <200710251044.l9PAi9Ag016224@xxxxxxxxxxxxxx>
- Thread-index: AcgW9CoahtrZg5c1RGuI2vHi0mpCKAAAx9SQ
- Thread-topic: Slow compdump on Vista - no .zcompdump created
For some reason the following line in compdump causes compdump to return
too early:
[[ -w ${_d_file:h} ]] || return 1
Commenting out this line resolves the problem: .zcompdump is created and
compinit now runs in less than a second.
For me, the above line was being executed with the following path:
+compdump:24> [[ -w /c/Users/johnc.CITRITE/Documents ]]
I can create files in this directory:
$ touch /c/Users/johnc.CITRITE/Documents/foo
$
.. although Cygwin seems to think it is not writeable:
$ ls -ld /c/Users/johnc.CITRITE/Documents
dr-x------+ 16 johnc mkpasswd 16384 Oct 25 12:10
/c/Users/johnc.CITRITE/Documents/
--- John.
-----Original Message-----
From: Peter Stephenson [mailto:pws@xxxxxxx]
Sent: 25 October 2007 11:44
To: Zsh Users
Subject: Re: Slow compdump on Vista - no .zcompdump created
"John Cooper" wrote:
> Still, it does seem odd that .zcompdump is not created by default.
> Presumably, if it were, compinit would likely run in a fraction of a
> second?
> Does anyone know why .zcompdump might not be getting created on
Cygwin,
> and whether I can force it?
Run "compdump" with "set -x" in effect (you'll probably have to add it
to the first "setopt" in the file) and see why it's not running the
"compdump" around line 493, or if it is why that's not doing anything.
You should be able to force a dump with "compinit -d", which takes an
option file argument to use for dumping.
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
Messages sorted by:
Reverse Date,
Date,
Thread,
Author