On Sat, Nov 28, 2009 at 7:05 PM, Steve Borho <[email protected]> wrote:
> On Sat, Nov 28, 2009 at 10:08 AM, Arve Knudsen <[email protected]>
> wrote:
> > Hi
> > How can I configure a private key file for tortoiseplink? In my
> > mercurial.ini (I'm on Windows) I've configured the ssh command so that my
> > key file is specified: "ssh = plink -ssh -i <key-file>". After I
> installed
> > TortoiseHG 0.9 however, tortoiseplink is used instead of straight plink,
> and
> > I have to authenticate by password.
>
> The system wide Mercurial.ini (in the install dir) specifies ui.ssh.
> You should be able to override this in your Mercurial.ini in your home
> directory.
>
> TortoisePlink should support Plink's command line arguments.
>
As I stated, I have configured the ssh command in ~\Mercurial.ini (in the
"ui" section), so that when I checked in before TortoiseHG was installed, I
authenticated with my key file (no need to type any password). Is it
possible then that TortoiseHG doesn't resolve my ~\mercurial.ini correctly?
On this particular machine my homedirectory is a network drive, so that
could complicate things. I see that, in Python, os.path.expanduser("~")
resolves to C:\Users\<user>, although %HOMEDRIVE% is M: (the intended
homedirectory). Mercurial apparently respects the latter, while I'm guessing
TortoiseHG uses a mechanism like os.path.expanduser? I think TortoiseHG
should get such parameters directly from Mercurial to ensure consistency.
Arve
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
