On Fri, Apr 29, 2016 at 10:11:48AM -0700, Junio C Hamano wrote: > Jeff King <p...@peff.net> writes: > > > I'm not sure if it's a good idea to go into so much detail about > > expand_user_path() here. There are a lot of options that use the same > > rules, and we probably don't want to go into a complete explanation > > inside each option's description. Is there a canonical definition of how > > we do expansion in config.txt that we can just reference (and if not, > > can we add one)? > > We have a dedicated section for various value-types used in the > configuration variables already, because we needed to describe how > booleans and scaled integers can be spelled, and the pathname type > would fit there. > > Documentation/config.txt | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/Documentation/config.txt b/Documentation/config.txt > index 59d7046..1bf42a6 100644 > --- a/Documentation/config.txt > +++ b/Documentation/config.txt > @@ -169,6 +169,11 @@ thing on the same output line (e.g. opening parenthesis > before the > list of branch names in `log --decorate` output) is set to be > painted with `bold` or some other attribute. > > +pathname:: > + A variable that takes a pathname value can be given a > + string that begins with "~/" or "~user/", and the usual > + tilde expansion happens to such a string. > + > > Variables > ~~~~~~~~~
Yeah, this is what I had in mind. My only reservation would be that we need to make sure it is clear that this applies only to keys marked as taking a "pathname" type in the documentation. I'm suspect there are ones that are logically paths but do not currently do the expansion, but the wording above makes it sound like any pathname-like thing does. Alternatively, it might be worth going through the list to make sure all paths use git_config_pathname() internally. Brian asked earlier if the "no expansion" was an intentional policy, but it's not. It's just that pathname expansion came much later, and config keys were ported over to it one by one as people found it useful to do so. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
