Symlinks are generally a bit iffy so I need to think alittle bit about scenarios here.

Usually you don't want to arbitrary eval these things. Thoughts@stigtsp?

Can run the test suite and probably iterate on it thought, thanks!

Yeah, I wasn't sure; maybe just warn if~/.ssh is not a directory, or if no keys were loaded, and/or make the path configurable (this comment might be better suited for#3 I realize).

Imho, an argument to the agent specifying a key dir makes more sense, for cases where you want keys to be stored somewhere else.

Yeah, I wasn't sure; maybe just warn if ~/.ssh is not a directory, or if no keys were loaded, and/or make the path configurable (this comment might be better suited for#3 I realize).

Lets implement--key-dir as a flag and rather warn if~/.ssh is a symlink :)

Would you be interested doing the work? It shouldn't be very hard.

Yeah, I wasn't sure; maybe just warn if ~/.ssh is not a directory, or if no keys were loaded, and/or make the path configurable (this comment might be better suited for#3 I realize).

Lets implement--key-dir as a flag and rather warn if~/.ssh is a symlink :)

Would you be interested doing the work? It shouldn't be very hard.

Sure! See latest commit. I rebased and added--key-dir and a warning. MovedGetSSHDir() to utils (couldn't think of anything better than misc at the moment, and it felt misc-y).

Looks great, thank you!

utils (couldn't think of anything better than misc at the moment, and it felt misc-y).

It could probably just stay insideutils.go frankly. No use having a single file for one function :)

It could probably just stay insideutils.go frankly. No use having a single file for one function :)

👍 renamed it

Thanks!