On Thu, May 7, 2009 at 8:12 AM, Shawn O. Pearce <spearce@xxxxxxxxxxx> wrote: > Stephen Boyd <bebarino@xxxxxxxxx> wrote: >> Only list the variables that can actually be affected by the command by >> searching the arguments for a config file setting. > > Wow, this is a lot of magic. > > Try: > > git config --global remote.gitster.url $(git config remote.o<TAB> > > You'll complete against --global, not the local repository. > Yeah, I didn't think it would be very robust. Is it a good idea to keep going down this path, or is it too magical? This example could be fixed by searching the words backwards, but I imagine there is some other case where that will fail. Also, --global and --system don't have values, so right now it's all wrong (i.e. config_file is "--global remote.gitster.url" for this example). -- 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