Re: Escape character for .gitconfig

From: Jeff King <peff@peff.net>
Date: Dec 18, 2011, 09:51 UTC
Message-ID: <20111218095120.GA2290@sigill.intra.peff.net>
In-Reply-To: <4EED9BE5.8060600@icefield.yk.ca>

On Sun, Dec 18, 2011 at 08:53:09AM +0100, Erik Blake wrote:

> That did the trick for this git newb. For the record, I had tried \(,
> /(, double- and single-quoting the entire path (note that git config
> --global had removed the quotes that were originally around the
> string). Did not think of "nested" quotes.

Yeah, if you are using "git config" to enter it on the command line, you'll have to put an extra layer of quoting around it to pass it through the shell you're currently running. That's why I showed the example as the actual config file text. :)

> Now, however, I have a different problem in that notepad++ is somehow
> signalling git that editing is complete before I even get a chance to
> edit the file. I am trying the command
> >git commit --amend

Yep. This is a general problem with editors that open files in an existing session. The only signal git has of the user being done editing is when when the editor process exits. For many editors, there is an option or other trick for sticking around until the file is closed.

I know nothing about notepad++, but a quick google turned up the "-multiInst" option, which would avoid attaching to the existing instance. That might work for you.

-Peff