Am 10.12.24 um 00:47 schrieb Junio C Hamano: > "M Hickford via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes: > >> From: Alejandro Barreto <alejandro.barreto@xxxxxx> >> +System >> +~~~~~~~~~~~~~~~~~~ >> +`HOME`:: >> + Specifies the path to the user's home directory. On Windows, if >> + unset, Git will set a process environment variable equal to: >> + `$HOMEDRIVE$HOMEPATH` if both `$HOMEDRIVE` and `$HOMEPATH` exist; >> + otherwise `$USERPROFILE` if `$USERPROFILE` exists. Makes sense and matches the implementation in compat/mingw.c. GfW uses the same method with with additional checks for existence of the $HOMEDRIVE$HOMEPATH combination. > I wondered what the reaction by the readers on non-Windows would be, > but hopefully they would read this to mean that HOME will not be > mucked with, even if they leave it unset (or they take it granted > that HOME is set somewhere while they log in and they do not have to > worry about it), so it may be OK. Since all Windows specific text is in a single sentence, I think it is difficult to misread. I would leave away the colon, though. > Just out of curiousity, is Git the only thing that uses $HOME on > Windows? Or among may other programs on Windows that use $HOME, is > the way Git gives a fall-back value out of these three variables > unusual and deserves documentation? No Windows native program uses $HOME. Only POSIX-derived tools would consider doing so. So, I would answer your question: yes, Git is the "only" one insisting in HOME being set. We are free to choose how we set it, and the way we do it makes the most sense for Git's purpose. It is certainly useful to document how we do it. -- Hannes
