From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Whaite <peta@cortexmachina.com>, zsh-workers@sunsite.auc.dk
Subject: PATCH: Re: cvs completion messy on dangling slink
Date: Thu, 20 Jul 2000 16:07:02 +0000 [thread overview]
Message-ID: <1000720160702.ZM2143@candle.brasslantern.com> (raw)
In-Reply-To: <200007201532.LAA32728@ursula.cortexmachina.com>
On Jul 20, 11:32am, Peter Whaite wrote:
}
} _cvs_modified_entries:stat:8: .#fuji-2.patch: no such file or directory
This should take care of it.
In the very general case, though, I still lament that there's no good way
to capture this kind of error output and present it via _message or some
other completion-friendly mechanism.
Index: Completion/User/_cvs
===================================================================
@@ -748,7 +748,7 @@
linedir="$match[1]"
realdir=${(e)~linedir}
[[ -f "$realdir"CVS/Entries ]] &&
- [[ -n ${pat::="${(@j:|:)${(@)${(@)${(@)${(@)${(@)${(@M)${(@f)"$(<"$realdir"CVS/Entries)"}:#/*}#/}/\\/[^\\/]#\\///}%/[^/]#/[^/]#}:#${(j:|:)~${${${${(f)"$(LC_ALL=C builtin stat -gn +mtime -F '%a %b %e %T %Y' ${realdir}*(D))"}##*/}/ //}//(#m)[][*?()<|^~#\\]/\\$MATCH}}}%%/*}//(#m)[][*?()<|^~#\\]/\\$MATCH}"} ]] &&
+ [[ -n ${pat::="${(@j:|:)${(@)${(@)${(@)${(@)${(@)${(@M)${(@f)"$(<"$realdir"CVS/Entries)"}:#/*}#/}/\\/[^\\/]#\\///}%/[^/]#/[^/]#}:#${(j:|:)~${${${${(f)"$(LC_ALL=C builtin stat -gn +mtime -F '%a %b %e %T %Y' ${realdir}*(D) 2>/dev/null)"}##*/}/ //}//(#m)[][*?()<|^~#\\]/\\$MATCH}}}%%/*}//(#m)[][*?()<|^~#\\]/\\$MATCH}"} ]] &&
_wanted files expl file _path_files -g "$pat"
else
_cvs_existing_entries
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-07-20 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 15:32 Peter Whaite
2000-07-20 16:07 ` Bart Schaefer [this message]
2000-07-21 7:18 PATCH: " Sven Wischnowsky
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=1000720160702.ZM2143@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=peta@cortexmachina.com \
--cc=zsh-workers@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).