Richard Lowe wrote:
> James Falkner <[EMAIL PROTECTED]> writes:
>> I "wish" (pun intended) openSolaris and/or Nevada had a wish->
>> symlink to point to whatever wish was the default (like it does
>> with /usr/bin/python).
>
> % uname -rv
> 5.11 snv_70
>
> % ls -l /usr/bin/wish
> lrwxrwxrwx 1
James Falkner <[EMAIL PROTECTED]> writes:
> S h i v wrote:
>
>> hgk uses "#!/usr/bin/env wish" to recognize the wish executable from the
>> path.
>>
>> Neither tclsh nor wish are installed to /usr/bin. They are part of sfw
>> and have been installed to /usr/sfw/bin/wish8.3 and
>> /usr/sfw/bin/tc
S h i v wrote:
> hgk uses "#!/usr/bin/env wish" to recognize the wish executable from the path.
>
> Neither tclsh nor wish are installed to /usr/bin. They are part of sfw
> and have been installed to /usr/sfw/bin/wish8.3 and
> /usr/sfw/bin/tclsh8.3 till recently.
>
> My current installation has
On 8/30/07, Danek Duvall <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 30, 2007 at 10:49:25PM +0530, S h i v wrote:
>
> > Below works just fine for me (first line of the hgk script was pointing to
> > wish and had to be changed to wish8.4)
>
> You mentioned that before. Why? /usr/bin/wish -> wish8.4.
On Thu, Aug 30, 2007 at 10:49:25PM +0530, S h i v wrote:
> Below works just fine for me (first line of the hgk script was pointing to
> wish and had to be changed to wish8.4)
You mentioned that before. Why? /usr/bin/wish -> wish8.4. Or is this
because your tcl/tk installation is in your path a
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Danek Duvall
> Sent: Thursday, August 30, 2007 9:48 PM
> To: Darren J Moffat
> Cc: John Rice; tools-discuss@opensolaris.org
> Subject: Re: [tools-discuss] hgk in mercurial
&
Danek Duvall wrote:
> On Thu, Aug 30, 2007 at 05:15:16PM +0100, Darren J Moffat wrote:
>
>> [extensions]
>> hgext.cdm=
>> hgext.hgk=/usr/lib/python2.4/vendor-packages/hgext/hgk.py
>
> You needed the full path here? It works for me without.
I did because I had $PYTHONPATH set to pickup cdm from
On Thu, Aug 30, 2007 at 05:15:16PM +0100, Darren J Moffat wrote:
> [extensions]
> hgext.cdm=
> hgext.hgk=/usr/lib/python2.4/vendor-packages/hgext/hgk.py
You needed the full path here? It works for me without.
Danek
___
tools-discuss mailing list
tools
Danek Duvall wrote:
> [hgk]
> path=/usr/demo/mercurial/hgk
>
> in your .hgrc as well as turning on the extension. Given that, I wonder if
> it should be in your path, anyway. It isn't on my gentoo box ...
That makes it work even if $CWD is at `hg root` but below it!
Cool thanks.
On sn
On Thu, Aug 30, 2007 at 11:48:37AM -0400, Richard Lowe wrote:
> That said, I don't think hgk should ever have been delivered broken.
That's why I put it in /usr/demo. Since you'd already have to go to the
trouble of installing a newer tcl/tk, you probably would be adept enough to
figure out what
"Cyril Plisko" <[EMAIL PROTECTED]> writes:
> While at this. Any plans to upgrade mercurial to 0.9.4 ?
>
Yes.
-- Rich
___
tools-discuss mailing list
tools-discuss@opensolaris.org
James Falkner <[EMAIL PROTECTED]> writes:
> I keep getting 'Error reading commits: hg: unknown command 'debug-rev-list'.
>
> Apparently hgk tries to run 'hg debug-rev-list' which is not a valid
> hg command, at least in 0.9.3. Googling is no help. Anyone have a clue what
> my problem is?
>
hgk u
James it's been a while since I set this up :( My own ~/.hgrc file has:
$ cat ~/.hgrc
[extensions]
hgk = /usr/lib/python2.4/vendor-packages/hgext/hgk.py
[hgk]
path = /usr/lib/python2.4/vendor-packages/hgext/hgk
I assume even if hgk is part of the mercurial delivered with nevada, you
will still
On 8/30/07, James Falkner <[EMAIL PROTECTED]> wrote:
> OK I got it to work by adding this to ~/.hgrc:
>
> [extensions]
> hgext.hgk=/usr/lib/python2.4/vendor-packages/hgext/hgk.py
I think the short form
hgext.hgk=
should be enough. At least it worked for me.
Since this extension is part of the SU
OK I got it to work by adding this to ~/.hgrc:
[extensions]
hgext.hgk=/usr/lib/python2.4/vendor-packages/hgext/hgk.py
Predumably that won't be needed if this functionality is added
to base Nevada.
-jhf-
Darren J Moffat wrote:
> James Falkner wrote:
>> I keep getting 'Error reading commits: hg:
James Falkner wrote:
> I keep getting 'Error reading commits: hg: unknown command 'debug-rev-list'.
>
> Apparently hgk tries to run 'hg debug-rev-list' which is not a valid
> hg command, at least in 0.9.3. Googling is no help. Anyone have a clue what
> my problem is?
I saw that as well.
The fir
Sorry James I haven't seen this error. My setup is:
bash-3.00$ uname -a
SunOS jmrlaptop 5.11 snv_67 i86pc i386 i86pc Solaris
bash-3.00$ hg version
Mercurial Distributed SCM (version 0.9.3)
Copyright (C) 2005, 2006 Matt Mackall <[EMAIL PROTECTED]>
This is free software; see the source for copying
I keep getting 'Error reading commits: hg: unknown command 'debug-rev-list'.
Apparently hgk tries to run 'hg debug-rev-list' which is not a valid
hg command, at least in 0.9.3. Googling is no help. Anyone have a clue what
my problem is?
-jhf-
John Rice wrote:
> +1 Currently hgk lives under /usr
Opps typo :
hgk lives under /usr/demo/mercurial
JR
John Rice wrote:
> +1 Currently hgk lives under /usr/demo/mercurial/bin/ and to invoke it
> on nevada you need to do the following which is a pain :(
>
> Install tcl/tk 8.4 and run from your hg managed project dir:
> $ export PATH=$PATH:/usr/de
+1 Currently hgk lives under /usr/demo/mercurial/bin/ and to invoke it
on nevada you need to do the following which is a pain :(
Install tcl/tk 8.4 and run from your hg managed project dir:
$ export PATH=$PATH:/usr/demo/mercurial/; wish8.4 /usr/demo/mercurial/hgk &
Having hgk view is really usef
Would there be any interest in incorporating hgk into the default hg
installation available in SX.
This is a tcl/tk based gui frontend available in contrib/ directory of
the mercurial sources.
hgk needs tcl/tk 8.4.x
Till recently SX had tcl/tk8.3. snv_70 is supposed to have moved from
8.3 to 8.4.
21 matches
Mail list logo
