# intended use of "git --exec-path"? 5 messages from 2007-10-24 to 2007-10-24. Participants: Scott Parish, Shawn O. Pearce, David Symonds, Andreas Ericsson. Thread: https://gitlist.dev/t/10445 ## Scott Parish, 2007-10-24 04:32 Subject: intended use of "git --exec-path"? Message-ID: <20071024043224.GR16291@srparish.net> URL: https://gitlist.dev/e/20071024043224.GR16291%40srparish.net ``` "git --exec-path" presently prints out the highest priority path to find executable in. That's a what; i'm curious why and when it should be used. Basically i'm wondering if its still useful, and what, if anything, it should be printing. Thanks sRp -- Scott Parish http://srparish.net/ ``` ## Shawn O. Pearce, 2007-10-24 04:38 Subject: Re: intended use of "git --exec-path"? Message-ID: <20071024043819.GI14735@spearce.org> URL: https://gitlist.dev/e/20071024043819.GI14735%40spearce.org In-Reply-To: <20071024043224.GR16291@srparish.net> ``` Scott Parish wrote: > "git --exec-path" presently prints out the highest priority path > to find executable in. That's a what; i'm curious why and when it > should be used. Basically i'm wondering if its still useful, and > what, if anything, it should be printing. git-gui uses it. git-gui runs git-* by prefixing it with the exec path. It also scans the first line of the file if we are on Windows and the "executable" doesn't end in ".exe" so it can figure out what process to run it through. So it really can't go away. -- Shawn. ``` ## Scott Parish, 2007-10-24 05:47 Subject: Re: intended use of "git --exec-path"? Message-ID: <20071024054749.GT16291@srparish.net> URL: https://gitlist.dev/e/20071024054749.GT16291%40srparish.net In-Reply-To: <20071024043819.GI14735@spearce.org> ``` On Wed, Oct 24, 2007 at 12:38:19AM -0400, Shawn O. Pearce wrote: > Scott Parish wrote: > > "git --exec-path" presently prints out the highest priority path > > to find executable in. That's a what; i'm curious why and when it > > should be used. Basically i'm wondering if its still useful, and > > what, if anything, it should be printing. > > git-gui uses it. git-gui runs git-* by prefixing it with the > exec path. It also scans the first line of the file if we are on > Windows and the "executable" doesn't end in ".exe" so it can figure > out what process to run it through. > > So it really can't go away. So it sounds like it might be more helpful for git to return its PATH, so other programs can set their PATH or search for executables accordingly. sRp -- Scott Parish http://srparish.net/ ``` ## David Symonds, 2007-10-24 05:54 Subject: Re: intended use of "git --exec-path"? Message-ID: URL: https://gitlist.dev/e/ee77f5c20710232254j32afa044t841b4a4f6fcdfd7d%40mail.gmail.com In-Reply-To: <20071024054749.GT16291@srparish.net> ``` On 10/24/07, Scott Parish wrote: > On Wed, Oct 24, 2007 at 12:38:19AM -0400, Shawn O. Pearce wrote: > > > Scott Parish wrote: > > > "git --exec-path" presently prints out the highest priority path > > > to find executable in. That's a what; i'm curious why and when it > > > should be used. Basically i'm wondering if its still useful, and > > > what, if anything, it should be printing. > > > > git-gui uses it. git-gui runs git-* by prefixing it with the > > exec path. It also scans the first line of the file if we are on > > Windows and the "executable" doesn't end in ".exe" so it can figure > > out what process to run it through. > > > > So it really can't go away. > > So it sounds like it might be more helpful for git to return its > PATH, so other programs can set their PATH or search for executables > accordingly. You don't necessarily want to be monkeying around with $PATH if you're trying to use a particular git installation (say, a build of next) instead of your "proper" install, which is in your $PATH; if you call /some/random/path/git-whatever, it should use the git tools in /some/random/path/, not in $PATH. Dave. ``` ## Andreas Ericsson, 2007-10-24 08:08 Subject: Re: intended use of "git --exec-path"? Message-ID: <471EFD78.6030206@op5.se> URL: https://gitlist.dev/e/471EFD78.6030206%40op5.se In-Reply-To: <20071024043224.GR16291@srparish.net> ``` Scott Parish wrote: > "git --exec-path" presently prints out the highest priority path > to find executable in. That's a what; i'm curious why and when it > should be used. Basically i'm wondering if its still useful, and > what, if anything, it should be printing. > git supports having all its "helpers" in a separate path. Since there were performance concerns with having scripts call the git wrapper for every invocation of every git program, the --exec-path option was added when the wrapper was rewritten in C. Unless it's a very tight loop that runs non-builtin programs, there's really no reason for scripts to use the git-whatever form of commands, but the ability to do so should probably be retained more or less forever. See 8e49d50388211a0f3e7286f6ee600bf7736f4814 for details. -- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 ```