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

Re: t7005 and vi in GIT_EXEC_PATH

From
Brian Gernhardt <benji@silverinsanity.com>
Date
Nov 10, 2007, 22:45 UTC
Message-ID
<443CE405-547F-4BBC-B32E-FFEE7E46700D@silverinsanity.com>
In-Reply-To
<85abpl69ck.fsf@lola.goethe.zz>
On Nov 10, 2007, at 5:09 PM, David Kastrup wrote:
Show 10 quoted lines
> Brian Gernhardt <benji@silverinsanity.com> writes:
>
>> If vi is in GIT_EXEC_PATH, then t7005-editor.sh fails because the  
>> real
>> vi is invoked instead of the test vi script.  This is because the git
>> wrapper puts GIT_EXEC_PATH ahead of ".".  I see no easy solution to
>> this problem, and thought I should bring it up with the list.
>
> Putting "." at the front of GIT_EXEC_PATH instead of PATH would appear
> to do the trick then, wouldn't it?

The GIT_EXEC_PATH I was referring to is the one set in the Makefile and compiled into git. The GIT_EXEC_PATH environment variable is set to the git repository. PATH ends up looking like this (paraphrased): "git.git:install directory:.:normal PATH". And since the install directory contains vi, the test fails (actually appears to hang because vi is waiting for input while it's output is being sent to / dev/null).

~~ Brian
Previous: David KastrupNext: Johannes Schindelin
Message 3 of 18 in “t7005 and vi in GIT_EXEC_PATH”
  1. Brian GernhardtNov 10, 2007
  2. David KastrupNov 10, 2007
  3. Brian GernhardtNov 10, 2007
  4. Johannes SchindelinNov 11, 2007
  5. Brian GernhardtNov 11, 2007
  6. Johannes SchindelinNov 11, 2007
  7. Junio C HamanoNov 11, 2007
  8. Use the best available exec path onlyBjörn Steinbrink, Nov 11, 2007
  9. Johannes SchindelinNov 11, 2007
  10. Jakub NarebskiNov 11, 2007
  11. Björn SteinbrinkNov 11, 2007
  12. Johannes SchindelinNov 11, 2007
  13. Junio C HamanoNov 11, 2007
  14. t7005-editor.sh: Don't invoke real vi when it is in GIT_EXEC_PATHBjörn Steinbrink, Nov 11, 2007
  15. Johannes SchindelinNov 11, 2007
  16. Brian GernhardtNov 11, 2007
  17. Johannes SchindelinNov 11, 2007
  18. Björn SteinbrinkNov 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.