From: Yves Frederix <yves.frederix@gmail.com>
To: zsh-users@zsh.org
Subject: Re: Zsh autocompletion with no access to a parent directory
Date: Fri, 25 Jun 2010 14:27:46 +0200 [thread overview]
Message-ID: <AANLkTimEGnzDEbA_1kFyoTcSRk7C95ehkUDnm8OrFkbp@mail.gmail.com> (raw)
Hi all,
I have recently switched from bash to zsh and I am loving it. However,
there are still issues I didn't experience with bash. One of them is
the fact that tabcompletion was not able to cross unreadable parent
directories. With the solution proposed in this thread, this now works
more or less, but not completely... The problem seems to be related to
the use of ~user to access the homedirectory of 'user'.
A minimal example:
testuser@dirac:~$ ls -ld Desktop/
drwx--x--x 3 testuser testuser 4096 2010-06-25 09:33 Desktop/
testuser@dirac:~$ ls -ld Desktop/work/
drwxr-xr-x 2 testuser testuser 4096 2010-06-25 09:33 Desktop/work/
testuser@dirac:~$ find Desktop/
Desktop/
Desktop/work
Desktop/work/file2
Desktop/work/file3
Desktop/work/file4
Desktop/work/file1
If I do (with accept-exact-dirs set to true):
yves@dirac ~$ ls ~testuser/Desktop/work/<tab><tab>
nothing happens.
However, using the full path name:
dirac ~$ ls /home/testuser/Desktop/work/<tab><tab>
dirac ~$ ls /home/testuser/Desktop/work/file
- files -
file1 file2 file3 file4
So now it works. What could be going on here, and is there a way to
make the form with ~ work as well? Thanks!
Cheers,
YVES
On Tue, 13 Apr 2010 09:33:15 -0700
Matt Wright <matt@xxxxxxxxxxxx> wrote:
> The situation is this: At work we make fairly heavy use of network home
> directories. In one particular case some important scripts live in
> ~foo/bin, however, the actually home directory of ~foo is not
> accessible. This appears to give _path_files a big headache, as trying to
> type the following results in no completion suggestions.
>
> # ~foo/bin/<TAB>
>
> As far as I can tell from my attempts to parse the debugging output, it
> is attempting to traverse ~foo for path expansion? I was attempting to look
> for a way to disable path expansion (the /u/l/b -> /usr/local/bin stuff)
> while leaving normal filename suggestion intact. Either that, or a way to
> alter _path_files such that it doesn't die in this situation.
You can try telling completion to accept any directory that it knows exists
without trying to expand the path:
zstyle ':completion:*' accept-exact-dirs true
I'm not sure if this will help in the case you're describing, however,
since it looks like it might not be able to tell if the directory exists.
You'll need zsh 4.3.
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
Tel: +44 (0)1223 692070 Cambridge Silicon Radio Limited
Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, UK
Member of the CSR plc group of companies. CSR plc registered in
England and Wales, registered number 4187346, registered office
Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4
0WZ, United Kingdom
next reply other threads:[~2010-06-25 13:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 12:27 Yves Frederix [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-13 16:33 Matt Wright
2010-04-13 16:45 ` Peter Stephenson
2010-04-13 17:11 ` Matt Wright
2010-04-13 20:33 ` Matt Wright
2010-04-14 9:14 ` Peter Stephenson
2010-04-14 9:47 ` Peter Stephenson
2010-04-14 10:01 ` Peter Stephenson
2010-04-14 17:20 ` Matt Wright
2010-04-23 15:01 ` Matt Wright
2010-04-23 21:44 ` Peter Stephenson
2010-04-29 21:38 ` Peter Stephenson
2010-04-29 22:14 ` Matt Wright
2010-04-30 8:32 ` Peter Stephenson
2010-04-30 16:05 ` Matt Wright
2010-05-05 4:55 ` Matt Wright
2010-05-05 9:58 ` Peter Stephenson
2010-07-29 15:46 ` Matt Wright
2010-08-03 12:59 ` Peter Stephenson
2010-04-30 16:14 ` Bart Schaefer
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=AANLkTimEGnzDEbA_1kFyoTcSRk7C95ehkUDnm8OrFkbp@mail.gmail.com \
--to=yves.frederix@gmail.com \
--cc=zsh-users@zsh.org \
/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).