From: Tanaka Akira <akr@m17n.org>
To: zsh-workers@sunsite.dk
Subject: support new .cvspass format in _cvs.
Date: 18 May 2001 03:19:13 +0900 [thread overview]
Message-ID: <hvoae4bkfdq.fsf@flux.etl.go.jp> (raw)
I found that .cvspass format is extended since cvs-1.11.1.
This patch support it in _cvs for completing cvsroots.
Index: Completion/Unix/Command/_cvs
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Unix/Command/_cvs,v
retrieving revision 1.3
diff -u -r1.3 _cvs
--- Completion/Unix/Command/_cvs 2001/05/10 09:19:33 1.3
+++ Completion/Unix/Command/_cvs 2001/05/17 18:15:41
@@ -614,7 +614,7 @@
id="$(LC_ALL=C ls -l "$cvspassfile")"
fi
if [[ "$id" != "$_cvs_pass_id" ]]; then
- _cvs_roots=($_cvs_roots ${${(f)"$(<$cvspassfile)"}%% *})
+ _cvs_roots=($_cvs_roots ${${${${(f)"$(<$cvspassfile)"}#/1 }%% *}/:2401\\//:/})
_cvs_pass_id="$id"
fi
fi
--
Tanaka Akira
reply other threads:[~2001-05-17 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=hvoae4bkfdq.fsf@flux.etl.go.jp \
--to=akr@m17n.org \
--cc=zsh-workers@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).