From: Alan Third <alan@idiocy.org>
To: zsh-users@sunsite.auc.dk
Subject: Possible bug in completion?
Date: Wed, 29 May 2002 00:37:02 +0100 [thread overview]
Message-ID: <20020528233702.GA15223@idiocy.org> (raw)
I'm using the debian zsh-beta package:
zsh 4.1.0-dev-4 (i686-pc-linux-gnu)
and I came across this little thing...
If I type something like:
for FILE in /v/o/in/so<tab>
Then that completes to:
for FILE in /var/oscar/incoming/sounds/
Which is right. But if I try and do the same thing again zsh seg
faults. I tried using zsh -f, and once compinit is loaded the above
still occurs:
grover:/home/alan>zsh -f
grover% autoload -U compinit
grover% compinit
grover% for FILE in /var/oscar/incoming/sounds/* ;do;done
grover% for FILE in /v/o/in/sozsh: segmentation fault zsh -f
If it's any help, /var/oscar is mounted using nfs from a remote
machine...
--
Alan Third
next reply other threads:[~2002-05-28 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 23:37 Alan Third [this message]
2002-05-29 0:29 ` Bart Schaefer
2002-05-29 6:40 ` Alan Third
2002-05-29 6:54 ` Borsenkow Andrej
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=20020528233702.GA15223@idiocy.org \
--to=alan@idiocy.org \
--cc=zsh-users@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).