From: Jeff King <peff@peff.net>
Date: Thu, 26 Apr 2012 06:19:23 GMT
Subject: Re: [PATCH v2] config: allow ~/ and ~user/ in include.path value
Message-ID: <20120426061923.GA22819@sigill.intra.peff.net>
In-Reply-To: <xmqqwr53bmc7.fsf@junio.mtv.corp.google.com>

On Wed, Apr 25, 2012 at 01:14:32PM -0700, Junio C Hamano wrote:

> > +found. The value of `include.path` is subject to tilde expansion: `~/`
> > +is expanded to the value of `$HOME`, and `~user/` to the specified
> > +user's home directory. See below for examples.
> >  
> >  Example
> >  ~~~~~~~
> > @@ -122,6 +124,7 @@ Example
> >  	[include]
> >  		path = /path/to/foo.inc ; include by absolute path
> >  		path = foo ; expand "foo" relative to the current file
> > +		path = ~/foo ; expand "foo" in your $HOME directory
> 
> Modulo s/~/{tilde}/ in the body text (but not in the displayed example),
> looked good to me, so I queued with two amends.

Thanks, I forgot about that.

I'd like to eventually stop building the documentation with
no-inline-literal. It was an asciidoc7 compatibility thing, but we can
probably drop that now. However, I suspect that would require us to
simultaneously convert all of the `{tilde}` uses back into `~`.

-Peff