From: Peter Stephenson <pws@csr.com>
To: zsh-users@sunsite.dk
Subject: Re: ClearCase version-extended filename completion
Date: Fri, 28 Feb 2003 14:01:55 +0000 [thread overview]
Message-ID: <4687.1046440915@csr.com> (raw)
In-Reply-To: "=?iso-8859-1?q?Hari=20Rao?="'s message of "Fri, 28 Feb 2003 12:57:23 GMT." <20030228125723.81445.qmail@web40105.mail.yahoo.com>
> Version-extended file names in ClearCase (e.g.,
> "foo.c@@/main/1") complete correctly (Type "foo.c@@/"
> and press tab) only while using old-style completion.
> No completions are displayed once you activate new
> style completions by calling "compinit." I understand
> from earlier threads* that this can be fixed by some
> changes to the "_files" function, but haven't been
> able to figure out the changes required. Has anyone
> already done this or can explain to me what needs to
> be done?
This is fixed in the latest 4.1 version (the main trunk) in the archive.
The patch was the one below. I don't know if it works in 4.0, but
there's a reasonable chance. It's had only limited testing, so any
feedback is useful.
Index: Completion/Unix/Type/_path_files
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Unix/Type/_path_files,v
retrieving revision 1.20
diff -u -r1.20 _path_files
--- Completion/Unix/Type/_path_files 6 Nov 2002 08:03:44 -0000 1.20
+++ Completion/Unix/Type/_path_files 12 Feb 2003 15:05:06 -0000
@@ -343,6 +343,22 @@
if [[ -n "$PREFIX$SUFFIX" ]]; then
# See which of them match what's on the line.
+ # pws non-canonical hack which seems to work so far...
+ # if we didn't match by globbing, check that there is
+ # something to match by explicit name. This is for
+ # `clever' filing systems where names pop into existence
+ # when referenced.
+ if (( ! $#tmp1 )); then
+ for tmp3 in "$tmp2[@]"; do
+ if [[ -n $tmp3 && $tmp3 != */ ]]; then
+ tmp3+=/
+ fi
+ if [[ -e "$tmp3${(Q)PREFIX}${(Q)SUFFIX}" ]] then
+ tmp1+=("$tmp3${(Q)PREFIX}${(Q)SUFFIX}")
+ fi
+ done
+ fi
+
if (( ! $#tmp1 )); then
tmp2=( ${^tmp2}/$PREFIX$SUFFIX )
elif [[ "$tmp1[1]" = */* ]]; then
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070
**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.
**********************************************************************
next prev parent reply other threads:[~2003-02-28 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 12:57 Hari Rao
2003-02-28 14:01 ` Peter Stephenson [this message]
2003-03-02 14:05 Hari Rao
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=4687.1046440915@csr.com \
--to=pws@csr.com \
--cc=zsh-users@sunsite.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).