zsh-workers
 help / color / mirror / code / Atom feed
* cvs completion messy on dangling slink
@ 2000-07-20 15:32 Peter Whaite
  2000-07-20 16:07 ` PATCH: " Bart Schaefer
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Whaite @ 2000-07-20 15:32 UTC (permalink / raw)
  To: zsh-workers


When I ask for completions on a `cvs commit' command I get:

 cvs commit _cvs_modified_entries:stat:8: .#colorcube: no such file or directory
_cvs_modified_entries:stat:8: .#fuji-2.patch: no such file or directory


Problem is the named .# files are symlinks to nowhere

    .#colorcube -> peta@ursula.cortexmachina.com.10716:960560451
    .#fuji-2.patch -> peta@ursula.cortexmachina.com.17118:1

and I have to confess I dont know how they got there as the repository is
local, not remote.  All I can think is that I scp'd them across from my remote
repository.

Anyway, assuming cvs is responsible for these slinks, then it would be nice to
have them handled gracefully.

This is RH6.2, zsh-3.1.9-dev-3, from todays cvs.
--
peta


^ permalink raw reply	[flat|nested] 3+ messages in thread

* PATCH: Re: cvs completion messy on dangling slink
  2000-07-20 15:32 cvs completion messy on dangling slink Peter Whaite
@ 2000-07-20 16:07 ` Bart Schaefer
  0 siblings, 0 replies; 3+ messages in thread
From: Bart Schaefer @ 2000-07-20 16:07 UTC (permalink / raw)
  To: Peter Whaite, zsh-workers

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   


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: PATCH: Re: cvs completion messy on dangling slink
@ 2000-07-21  7:18 Sven Wischnowsky
  0 siblings, 0 replies; 3+ messages in thread
From: Sven Wischnowsky @ 2000-07-21  7:18 UTC (permalink / raw)
  To: zsh-workers


Bart Schaefer wrote:

> 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.

Yes. Any ideas for how to do that?

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2000-07-21  7:18 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-07-20 15:32 cvs completion messy on dangling slink Peter Whaite
2000-07-20 16:07 ` PATCH: " Bart Schaefer
2000-07-21  7:18 Sven Wischnowsky

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).