git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/2] http: expand http.cookieFile as a path

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 29, 2016, 17:11 UTC
Message-ID
<xmqqziscz6ej.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160429141212.GB26643@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 6 quoted lines
> 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
 ~~~~~~~~~
Previous: Junio C HamanoNext: Jeff King
Message 10 of 12 in “Documentation: config: improve word ordering for http.cookieFile”
  1. 1/2 Documentation: config: improve word ordering for http.cookieFileBrian Norris, Apr 29, 2016
  2. 2/2 http: expand http.cookieFile as a pathBrian Norris, Apr 29, 2016
  3. Jeff KingApr 29, 2016
  4. Brian NorrisApr 29, 2016
  5. Junio C HamanoApr 29, 2016
  6. Jeff KingApr 29, 2016
  7. Junio C HamanoApr 29, 2016
  8. Jeff KingApr 29, 2016
  9. Junio C HamanoApr 29, 2016
  10. Junio C HamanoApr 29, 2016
  11. Jeff KingApr 29, 2016
  12. Junio C HamanoApr 29, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.