OK, let me re-phrase. I assume it’s a bug that Julia doesn’t find my home directory?
This applies not only to git configuration, as it turns out - if I, for example, put a .juliarc file in my home directory, it isn’t run on startup (I assume because Julia has no indication anywhere that it should look in the folder where it resides). So there’s something fishy here. On Windows, %USERPROFILE% is more-or-less directly corresponding to posix $HOME, so perhaps Julia should do something like ENV["HOME"] = get(ENV, "HOME", ENV["USERPROFILE"]) at startup on Windows? // T On Thursday, October 15, 2015 at 2:20:07 PM UTC+2, Tony Kelman wrote: Not necessarily, git-bash is a posix login shell. Windows doesn't usually > set HOME, we use it if set in Julia but have a fallback for when it isn't. > On Oct 14, 2015 11:28 PM, "Tomas Lycken" <[email protected] > <javascript:>> wrote: > >> Good catch! >> >> # in git bash >> $ echo $HOME >> /c/Users/Tomas Lycken >> >> # in Julia 0.4 >> julia> ENV["HOME"] >> ERROR: KeyError: HOME not found >> in getindex at env.jl:37 >> >> julia> ENV["HOME"] = "C:\\Users\\Tomas\ Lycken\\" >> "C:\\Users\\Tomas Lycken\\" >> >> julia> Pkg.update() >> INFO: Updating METADATA... >> INFO: Updating Benchmarks... >> INFO: Updating DualNumbers... >> INFO: Updating LightGraphs... >> INFO: Updating Contour... >> INFO: Updating Interpolations... >> INFO: Updating ZMQ... >> INFO: Computing changes... >> INFO: No packages to install, update or remove >> >> So, ENV["HOME"] wasn’t set, and setting it fixed this. I assume it’s a >> bug that it wasn’t set? >> >> // T >> >> On Wednesday, October 14, 2015 at 5:59:51 PM UTC+2, Tony Kelman wrote: >> >> I'm not sure. When you run in git-bash, is the environment variable HOME >>> set? If you set it in Julia, does it change anything? >>> >>> >>> On Wednesday, October 14, 2015 at 2:10:48 AM UTC-7, Tomas Lycken wrote: >>>> >>>> Thanks! That was a useful pointer, and it got me someways down the >>>> road, but I still see really weird things... >>>> >>>> Without me (knowingly) changing anything, I went into the Julia install >>>> folder, into Git, and double-clicked git-bash.cmd. That opened a bash >>>> shell, in which I could cd to e.g. the METADATA.jl package directory and >>>> do >>>> git pull. It asked me to accept the server's fingerprint, but otherwise >>>> didn't complain. git pull worked then without error. >>>> >>>> After doing this, I started a new Julia 0.4.0 instance, and now >>>> Pkg.update() works - once. The second time, it borked on a couple of >>>> repositories which I have forked, but where my fork is not the "main >>>> source", with the message "error: could not fetch tlycken" (which is the >>>> name of my fork in the output of `git remote -v`; I still have a remote >>>> called origin). Manually going into those package directories using >>>> git-bash, and manually saying `git fetch tlycken`, completes without error. >>>> >>>> If Julia is using the same git as the git-bash from Julia's >>>> installation folder, why can one fetch without problem, while the other is >>>> denied permission? >>>> >>>> // T >>>> >>>> >>>> On Wednesday, October 14, 2015 at 10:34:00 AM UTC+2, Tony Kelman wrote: >>>>> >>>>> The Win and Mac binaries bundle their own git, rather than relying on >>>>> having it manually installed and on the path. Check the Git folder under >>>>> the Julia install, run the git-bash there to try getting keys working. >>>> >>>> >> >
