2007/5/29, Johannes Sixt <J.Sixt@xxxxxxxxxxxxx>:
> I get that here too, no matter what I set the mount point to be, and > without the fstab file at all. When I inserted '/usr/bin/sort' I had checked for 'which sort' on my Linux and it gave me /usr/bin/sort. Now I see that /bin/sort is probably the canonical path to sort on any *nix. Will change that. But is this also true for 'find'?
I suggest that you add $PATH appropriately (prepending /bin and /usr/bin/ ) and then let the OS figure it out. The other option is to write an autoconf test to discover the proper path.
> Also, the /bin/gitk.bat file should rather be > @"%~d0%~p0wish84.exe" "%~d0%~p0gitk" %* > than the current hardcoded path. (Probably won't work with > command.com, but who uses that for development nowadays anyways, right ;-) Nice trick! But don't try this at home without parental guidance! It fills your screen with recursive console window invocations of itself. I put this into gitk.cmd (didn't try .bat): @start wish84.exe "%~d0%~p0gitk" %* assuming wish84 is in the PATH (which is probably a sane assumption because either it is part of the installer, in which case it should have set up the PATH, or you have Tcl/Tk installed for some other reason, in which case you will want to have it in the PATH, too). Futhermore, I like to have the GUI sent into the background automatically and without opening another console window, hence, the use of 'start'.
I'll have a look at this when I have time. What the hell is %~d0%~p0 ? -- Han-Wen Nienhuys - hanwen@xxxxxxxxx - http://www.xs4all.nl/~hanwen - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
