From: Matt Wright <matt@sysctl.co.uk>
To: zsh-users@zsh.org
Subject: Zsh autocompletion with no access to a parent directory
Date: Tue, 13 Apr 2010 09:33:15 -0700 [thread overview]
Message-ID: <3663DC29-7A8F-4A0C-8262-5FFE701C8E3A@sysctl.co.uk> (raw)
Hey,
I've run into a problem with autocompletion and I can't seem to find anything about it from googling. Hopefully someone might be able to help.
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.
Any ideas?
Regards,
Matt
next reply other threads:[~2010-04-13 16:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 16:33 Matt Wright [this message]
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
2010-06-25 12:27 Yves Frederix
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=3663DC29-7A8F-4A0C-8262-5FFE701C8E3A@sysctl.co.uk \
--to=matt@sysctl.co.uk \
--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).