On Saturday 04 November 2006 19:49, Steven E. Harris wrote:
> This seems like a case of the tools trying to be too smart. If the
> candidate paths offered to zsh are
>
> src/foo/bar/baz.h
> obj/obj1.0
>
> one would expect that just seeing the leading 's' or 'o' would be
> enough to complete the right choice. I'm surprised that zsh /appears/
> to splitting the candidates into path components and filtering them
> piece-by-piece -- or something like that.
No, it's not zsh itself, but the current mtn zsh completion code.
Can you please try the attached (trivial) patch and see whether that behaves
the way you expect? It enables completion of complete paths. Performance
might be a problem, though, and if it is, we might try the other solution I
mentioned earlier (completing in cwd, and additionally completing all
directories).
Regards,
Thomas
--
HOST SYSTEM NOT RESPONDING, PROBABLY DOWN. DO YOU WANT TO WAIT? (Y/N)
#
# old_revision [a79f203730daf07c0a2dc09fd3e31efafbd088e7]
#
# patch "contrib/monotone.zsh_completion"
# from [a86dcb057415672ee67fc20465fd00749ef09191]
# to [0068d1dcb559cc21ed77208599eeabbfbc17f733]
#
============================================================
--- contrib/monotone.zsh_completion a86dcb057415672ee67fc20465fd00749ef09191
+++ contrib/monotone.zsh_completion 0068d1dcb559cc21ed77208599eeabbfbc17f733
@@ -402,7 +402,7 @@ _mtn_files() {
local prefix=${PREFIX}X
local rcwd="$(_mtn_rcwd)"
local -a list
- list=( ${${${(f)"$(mtn ls --depth=0 $1 ${prefix:h} 2>/dev/null)"}#$rcwd}#/} )
+ list=( ${${${(f)"$(mtn ls $1 ${prefix:h} 2>/dev/null)"}#$rcwd}#/} )
compadd -f -a list
}
_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel
