Re: RFC: a plugin architecture for git extensions?

From: Jeff King <peff@peff.net>
Date: May 9, 2011, 07:35 UTC
Message-ID: <20110509073535.GA5657@sigill.intra.peff.net>
In-Reply-To: <BANLkTikDVBgOqd1U=qSL99U3K8EtLVTxtw@mail.gmail.com>

On Sun, May 08, 2011 at 02:44:54PM +1000, Jon Seymour wrote:

Show 8 quoted lines

> >  4. Users can set GIT_PLUGIN_PATH in the environment if they want to do
> >     something fancy (they can also always just set PATH and MANPATH
> >     manually if they want, too).
> 
> If the need for multiple plugin directories were accepted, then I
> wonder if there might not be some advantages for the configuration of
> this path being in git configuration rather than an environment
> variable?

I think in general most users would not need to set this (since after all, the point of your proposal is to avoid such tweaks), so it may not be worth troubling about. But it is much simpler to tell users to run:

  git config core.pluginpath /path/to/wherever

than trying to figure out whether they need to use bashrc, cshrc, whatever Windows uses, etc.

-Peff