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

Re: [PATCH 0/3] git-help -i (info): finishing touches

From
Christian Couder <chriscool@tuxfamily.org>
Date
Dec 11, 2007, 05:22 UTC
Message-ID
<200712110622.51583.chriscool@tuxfamily.org>
In-Reply-To
<7v8x42n9s4.fsf@gitster.siamese.dyndns.org>
Le lundi 10 décembre 2007, Junio C Hamano a écrit :
> Junio C Hamano <gitster@pobox.com> writes:
> > This series attempts to add finishing touches to "git help -i" (info)
> > support.
It looks like the patch series you talk about was not sent to the list.
In the last patch there is:
diff --git a/help.c b/help.c
index 9d7ad6f..c96b167 100644
--- a/help.c
+++ b/help.c
@@ -286,6 +286,7 @@ static void show_man_page(const char *git_cmd)
 static void show_info_page(const char *git_cmd)
 {
        const char *page = cmd_to_page(git_cmd);
+       setenv("INFOPATH", GIT_INFO_PATH, 1);
        execlp("info", "info", "gitman", page, NULL);
 }

But I wonder if something like this would be better:

diff --git a/help.c b/help.c
index c96b167..933d850 100644
--- a/help.c
+++ b/help.c
@@ -255,23 +255,23 @@ static const char *cmd_to_page(const char *git_cmd)
        }
 }

-static void setup_man_path(void)
+static void prepend_to_env_path(const char *name, const char *value)
 {
        struct strbuf new_path;
-       const char *old_path = getenv("MANPATH");
+       const char *old_path = getenv(name);

        strbuf_init(&new_path, 0);

        /* We should always put ':' after our path. If there is no
-        * old_path, the ':' at the end will let 'man' to try
-        * system-wide paths after ours to find the manual page. If
+        * old_path, the ':' at the end will let some commands
+        * like 'man' to try system-wide paths after ours. If
         * there is old_path, we need ':' as delimiter. */
-       strbuf_addstr(&new_path, GIT_MAN_PATH);
+       strbuf_addstr(&new_path, value);
        strbuf_addch(&new_path, ':');
        if (old_path)
                strbuf_addstr(&new_path, old_path);

-       setenv("MANPATH", new_path.buf, 1);
+       setenv(name, new_path.buf, 1);

        strbuf_release(&new_path);
 }
@@ -279,14 +279,14 @@ static void setup_man_path(void)
 static void show_man_page(const char *git_cmd)
 {
        const char *page = cmd_to_page(git_cmd);
-       setup_man_path();
+       prepend_to_env_path("MANPATH", GIT_MAN_PATH);
        execlp("man", "man", page, NULL);
 }

 static void show_info_page(const char *git_cmd)
 {
        const char *page = cmd_to_page(git_cmd);
-       setenv("INFOPATH", GIT_INFO_PATH, 1);
+       prepend_to_env_path("INFOPATH", GIT_INFO_PATH);
        execlp("info", "info", "gitman", page, NULL);
 }

Tell me if you want a proper path.

Christian.
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 3 in “Re: [PATCH 0/3] git-help -i (info): finishing touches”
  1. Junio C HamanoDec 10, 2007
  2. Christian CouderDec 11, 2007
  3. Junio C HamanoDec 11, 2007

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.