From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26210 invoked by alias); 2 Dec 2014 15:54:59 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 33832 Received: (qmail 2079 invoked from network); 2 Dec 2014 15:54:57 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, SPF_HELO_PASS,T_HDRS_LCASE,T_MANY_HDRS_LCASE autolearn=ham version=3.3.2 X-AuditID: cbfec7f5-b7fc86d0000066b7-22-547de0ceb140 Date: Tue, 02 Dec 2014 15:54:52 +0000 From: Peter Stephenson To: Zsh Hackers' List Subject: Something rotten in tar completion Message-id: <20141202155452.647182b4@pwslap01u.europe.root.pri> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrMJMWRmVeSWpSXmKPExsVy+t/xa7rnHtSGGLQcELY42PyQyYHRY9XB D0wBjFFcNimpOZllqUX6dglcGf/Pb2MvaOesuH3tMXMDYx97FyMnh4SAicTNbU8ZIWwxiQv3 1rN1MXJxCAksZZRoWzWbBcJZziTx5XAbG0gVi4CqxIqX08E62AQMJaZumg1kc3CICGhLtH8U AwkLA5m3Dt9kBQnzCthLbNlWBBLmF9CXuPr3ExPELnuJmVfOgE3hFRCU+DH5HguIzSygJbF5 WxMrhC0vsXnNW+YJjHyzkJTNQlI2C0nZAkbmVYyiqaXJBcVJ6blGesWJucWleel6yfm5mxgh AfV1B+PSY1aHGAU4GJV4eB3e1YQIsSaWFVfmHmKU4GBWEuH9ZVwbIsSbklhZlVqUH19UmpNa fIiRiYNTqoFR8Lvd/B8c7Wni5aqlEjlmfl3ffryccKb3H+OK9C+XZ8tX2aw+0CoVYmB0rX5+ YDPjhEcHXyxYMPdY8nP3Y0LR3Ukae29qsbzlWWJl7vNxyrK8Zr89HUIH2ty4TZkX8M04b/zW oUno3R+zsw+lxXZce8ObXWZ8a9PpFYyTGj+X22VeeVV4WfKIEktxRqKhFnNRcSIAsLpzmgYC AAA= I've been seeing this for some time and haven't had a chance to look any further, given which it's high time I reported it in any case in the unlikely event someone's got some spare time. If I try to complete after "tar xvzf ...", which is where I usually am completing (I don't tend to bother completing inside tar files), it's *incredibly* slow. I suspect it's looking in the file, which it doesn't need to at this point --- it's only completing the name of the file. (It doesn't even know what file I'm using yet, in fact.) Note this is a bog standard local disk. What's even worse is I can't abort. If I ^C it simply says "Killed after 41 seconds" but doesn't stop; if I do it repeatedly the time taken increments but that's all. It does finish eventually after a few minutes and give the right answer it should have given in a small fraction of a second. As far as I can see there's no remaining sign I tried to abort it. Haven't looked at whether my options and styles come into it, but will if nobody else is seeing this (it's pretty darned obvious). This is with the latest version, in case you hadn't guessed. pws