Thomas Rast <trast@xxxxxxxxxxxxxxx> wrote: > This is still RFC because, as you can see in the code below, I tried > to avoid completing at all while the user still needs to supply a > regex. Sadly, bash turns the COMPREPLY=() into filename completion > anyway. Is there a way to prevent this? Not that I know of. You can turn off default filename completion when you register the completion function, but that then breaks like every other git command for completion support because a lot of them do want to complete filenames. > + local i c=1 have_regex="" > + while [ $c -lt $COMP_CWORD ]; do > + i="${COMP_WORDS[c]}" > + case "$i" in > + -e) ;; > + -e*) have_regex="$c" ; break ;; > + -*) ;; > + *) have_regex="$c"; break ;; > + esac > + c=$((++c)) > + done What happens with `git grep -e a -e b`? Do we trigger into ref completion too early when we should still be doing the regex completion? -- Shawn. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html