From: Will Yardley <william@hq.newdream.net>
To: zsh-users@sunsite.auc.dk
Subject: Re: zsh: completion over nsf file systems
Date: Tue, 14 Aug 2001 11:47:00 -0700 [thread overview]
Message-ID: <20010814114700.J19688@hq.newdream.net> (raw)
In-Reply-To: <3B794CDE.F771561D@cfdrc.com>
virgil adumitroaie wrote:
> i have started using zsh recently. all is wonderful (i am very happy about
> xterm title bars, works wonders for gnome users) except one difference
> between zsh and bash which i cannot eliminate. file name completion works
> under bash even for nsf file systems but not under zsh. for example,
> issuing
> ls /hosts/other_machine/exported_directory/<TAB>
> under bash I would be able to see the subdirectories, but under zsh not.
> is this something that can be configured with compctl and if yes, how?
you might want to try messing around with your options; i really doubt that
the problem has anything to do with nfs - we use nfs to mount netapps and
other filesystems on almost all of our machines, and i've never had a problem
with completion.
you might try:
bash_auto_list
no_menu_complete
no_auto_menu
that's what i have.
are there a lot of files in the directory you're trying to look at? i was
testing this out and it did take a while to get to:
zsh: do you wish to see all 266 possibilities (67 lines)?
- so it might just be taking a while to figure out all the files / directory
names. if you are using color ls or 'ls -F' or anything you might try
/bin/ls /hosts/other_machine/exported_directory/<TAB>
and see if that's any speedier.
w
--
Sintax error in config file! (line 378)
aborted!
prev parent reply other threads:[~2001-08-14 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 16:07 virgil adumitroaie
2001-08-14 16:47 ` Vincent Lefevre
2001-08-14 18:47 ` Will Yardley [this message]
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=20010814114700.J19688@hq.newdream.net \
--to=william@hq.newdream.net \
--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).