From: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
To: zsh-workers@sunsite.auc.dk
Subject: Lockup on tab completion with compinit+list_packed
Date: Sun, 6 May 2001 16:51:06 +0200 [thread overview]
Message-ID: <20010506165106.A4154@kallisto.sind-doof.de> (raw)
Hi,
Recently zsh totally locked up using 100% CPU on doing a tab
completion.
I can reproduce this actually with (running zsh -f):
kallisto% echo $ZSH_VERSION
3.1.9-dev-8
kallisto% ls
alsa-modules-2.4.4-int1-vlan101-nf20010428_0.5.10b-4+p3+1.kallisto.0_i386.deb
alsa-modules-2.4.4-int1-vlan101-nf20010428_0.5.10b-4+p3+2.kallisto.0_i386.deb
alsa-modules-2.4.4-int1-vlan101-nf20010504_0.5.10b-4+p3+1.kallisto.0_i386.deb
kallisto% autoload compinit
kallisto% compinit
kallisto% setopt list_packed
kallisto% ls <----- here it locks up on pressing TAB once, after the space
If I leave out "setopt list_packed", completion works fine, as does
without the "compinit". Only the combination of the two (in any order)
leads to lockup.
The odd is, with another set of files, with very similar names, it
works perfectly well. For example:
kallisto% ls alsa-modules-2.4.3-ac
^<TAB>
On first tab, it completes up to the "-ac". If I then continue to type
in the name and eventually try completing again, everything is fine
for the files
alsa-modules-2.4.3-ac1_0.5.10b-4+p3+kallisto.1.0_i386.deb
alsa-modules-2.4.3-ac14-int1-vlan101-nf20010426-swapb3_0.5.10b-4+p3+1.kallisto.0_i386.deb
alsa-modules-2.4.3-ac1-dc_0.5.10b-4+p3+kallisto.1.0_i386.deb
but it locks up again for
alsa-modules-2.4.3-ac4-int1-nf20010411-dc1_0.5.10b-4+p3+kallisto.1.0_i386.deb
alsa-modules-2.4.3-ac4-int1-nf20010411-dc1_0.5.10b-4+p3+kallisto.1.1_i386.deb
alsa-modules-2.4.3-ac5-int1-nf20010413-dc1_0.5.10b-4+p3+kallisto.1.0_i386.deb
(regardless of how much of the filename I actually typed in)
If I press <TAB> twice after getting to the "-ac", all 6 files show up
fine in the listing.
If I [sl]trace the locked process, no activity shows up, so the
process seems to be doing some internal calculations in an endless
loop. Due to time constraints, I could not look any closer on the
problem.
Please contact me if you need any further information or if I should
do any further investigation.
Andreas
PS: Please Cc me on replies as I don't read the mailinglist.
--
<SomeLamer> what's the difference between chattr and chmod?
<SomeGuru> SomeLamer: man chattr > 1; man chmod > 2; diff -u 1 2 | less
-- Seen on #linux on irc
next reply other threads:[~2001-05-06 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 14:51 Andreas Ferber [this message]
2001-05-06 23:59 ` Bart Schaefer
2001-05-07 8:10 ` Sven Wischnowsky
2001-05-14 6:12 ` Andreas Ferber
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=20010506165106.A4154@kallisto.sind-doof.de \
--to=aferber@techfak.uni-bielefeld.de \
--cc=zsh-workers@sunsite.auc.dk \
/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).