Application: TortoiseHg
Category: Development
Description: TortoiseHg is a set of graphical tools for the Mercurial distributed revision control system.
Download TortoiseHg Portable 2.7 Development Test 1 [17.5 MiB download / 35.5 MiB installed]
(MD5: 642bba171861914361fec25e73613888)
Release Notes:
2.7 Development Test 1 (2013-02-11): updated TortoiseHg to v2.7 (Mercurial 2.4.2+)
2.6.2 Development Test 1 (2013-01-05): updated TortoiseHg to v2.6.2 (Mercurial 2.4.2)
2.6.0 Development Test 1 (2012-11-22): updated TortoiseHg to v2.6 (Mercurial 2.4); added TortoisePlink to the no-compress list
2.4.2 Development Test 1 (2012-07-07): updated TortoiseHg to v2.4.2 (Mercurial 2.2.3)
2.4.1 Development Test 1 (2012-06-10): updated TortoiseHg to v2.4.1 (Mercurial 2.2.2)
2.4 Development Test 1 (2012-05-21): updated TortoiseHg to v2.4 (Mercurial 2.2.1)
2.3.1 Development Test 1 (2012-03-18): updated TortoiseHg to v2.3.1 (Mercurial 2.1.1)
2.2.2 Development Test 1 (2012-01-04): updated TortoiseHg to v2.2.2 (Mercurial 2.0.2)
2.2.1 Development Test 1 (2011-12-22): updated PAL to 3.0 Dev; updated TortoiseHg to v2.2.1 (Mercurial 2.0.1); switched to custom TortoisePlink portable build
2.2 Development Test 1 (2011-11-09): updated PAL to 2.2/tip; updated TortoiseHg to v2.2 (Mercurial 2.0)
2.1.4 Development Test 1 (2011-10-23): updated TortoiseHg to v2.1.4 (Mercurial 1.9.3); added option to disable Python bytecode files creation
2.1.2 Development Test 1 (2011-08-02): updated TortoiseHg to v2.1.2 (Mercurial 1.9.1); added PYTHONDONTWRITEBYTECODE
2.1.1 Development Test 1 (2011-07-07): updated TortoiseHg to v2.1.1 (Mercurial 1.9+10); bundled Visual Studio runtimes; fixed code to set the location of PuTTY.rnd; changed path to TortoisePlink.exe in order to support directories with spaces in the name.
2.1 Development Test 1 (2011-07-02): updated TortoiseHg to v2.1 (Mercurial 1.9); added AppCompactor.ini.
2.0.5 Development Test 2 (2011-06-12): added App\TortoiseHg to %Path%; added the entire HgRc.d directory to the search path.
2.0.5 Development Test 1 (2011-06-10): initial release
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
App\TortoiseHgdirectory to%Path%. The command prompt should now work properly.HgRc.ddirectory to the search path. This enables automatic merge tools detection.Previously known as kAlug.
I'm glad to see this as a portable app. Just out of curiosity, how did you keep it from creating its shell-integration Registry entries? All I could find in your launcher was the -nofork command-line option.
Portability looks good, PortableApps Format validation passed, and all functionality seems to be intact. Oh, and help.html displayed correctly for me in Iron.
Nice work.
"The question I would like to know, is the Ultimate Question of Life, the Universe and Everything. All we know about it is that the Answer is Forty-two, which is a little aggravating."
Good to know that everything worked fine for you.
Regarding the shell extension, I simply didn't installed it.
Previously known as kAlug.
Updated to TortoiseHg 2.1 / Mercurial 1.9.
Tip: to use custom extensions, put them somewhere in the
Datadirectory and use~, e.g.Data\customExtension->customExtension=~/customExtension.Previously known as kAlug.
Updated to TortoiseHg 2.1.1 / Mercurial 1.9+10.
Also bundled the Visual C++ Run-Times and fixed some paths.
Previously known as kAlug.
I've continued using this and it's working quite well. As far as I can tell, everything does what it's supposed to; I've done things ranging from pushing to pulling to patching to cloning, and it's all succeeded.
There was one bit of weirdness - I tried pushing changes shortly after being added to a project on SourceForge and TortoiseHg completely failed. It wouldn't even put up a password dialog. I ended up having to create a SSH key, launch Pageant, and then TortoiseHg properly pushed the changes. Oddly enough, it's requested my password ever since, and the SSH key hasn't been necessary. I don't know if that's TortoiseHg itself or a bug with the portable package, but I thought I'd mention it.
Oh, speaking of Pageant, I'd be appreciative if you could create a launcher for that too. I'm fairly sure it doesn't need anything special - I had no trouble running it directly from App\TortoiseHg - but a launcher would be nice to have.
Thanks!
"The question I would like to know, is the Ultimate Question of Life, the Universe and Everything. All we know about it is that the Answer is Forty-two, which is a little aggravating."
We can call TortoiseHg from Pageant. The problem is, how to tell Pageant to close?
Regarding your problem, I never had it (and I use passwords too). Maybe it's related to Pageant?
Previously known as kAlug.
I don't think the original issue was with Pageant, since I didn't try running it until after I'd struggled with TortoiseHg for awhile. It's probably just a newb/one-time issue, so if nobody else experiences it, go ahead and ignore.
To shut down Pageant, maybe just send the WM_QUIT message? I know that's a bit messy, but it doesn't look like Pageant provides a built-in way to shut down cleanly.
"The question I would like to know, is the Ultimate Question of Life, the Universe and Everything. All we know about it is that the Answer is Forty-two, which is a little aggravating."
I've checked the Pageant's source, and really there's no way to tell it to close.
I've come with this:
!include WinMessages.nsh FindWindow $R0 Pageant Pageant SendMessage $R0 ${WM_CLOSE} 0 0 # just close Pageant, or SendMessage $R0 ${WM_COMMAND} 16 0 # use its internal mechanism, closing passwords dialogs tooPreviously known as kAlug.
There are two decisions to be made:
PYTHONDONTWRITEBYTECODEbe permanent or added as a option inAppNamePortable.ini?Previously known as kAlug.
For Pageant, I'd say your second method is probably best if that's what Pageant uses internally.
SendMessage $R0 ${WM_COMMAND} 16 0 # use its internal mechanism, closing passwords dialogs tooWhat does
PYTHONDONTWRITEBYTECODEdo? My quick web search didn't turn up much."The question I would like to know, is the Ultimate Question of Life, the Universe and Everything. All we know about it is that the Answer is Forty-two, which is a little aggravating."
We need to be careful to not close other instances. I'd like to know what John has to say about it.
The
PYTHONDONTWRITEBYTECODEenvironment variable prevents the writing of.py[co]files. This is useful to avoid writing unnecessarily to the device. It's mostly useful with plugins cloned from a repository: the presence of new files can require a manual pull/merge.Previously known as kAlug.
Maybe use
SingleAppInstanceto make sure there are no other instances?I'd say
PYTHONDONTWRITEBYTECODEshould be on by default if it gives things a major speed boost, but it would be nice to have the ability to turn it off as well."The question I would like to know, is the Ultimate Question of Life, the Universe and Everything. All we know about it is that the Answer is Forty-two, which is a little aggravating."
I meant other instances of Pageant, including local ones.
I'll put
PYTHONDONTWRITEBYTECODEas an option onAppNamePortable.ini.Previously known as kAlug.
I've been thinking on removing Pageant from THGp, and somehow include it on PuTTY Portable. Opinions, please.
Previously known as kAlug.
I've been meaning to get round to improving PuTTY Portable to work nicely with pageant. Pageant should be in there, not in this.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
But then we have some problems:
Previously known as kAlug.
I don't see why we would need multiple launchers. I would have Pageant be an add-on installer for PuTTY which just contains App\PuTTY\pageant.exe, and have PuTTY Portable launch it if it exists.
What data does plink need to deal with? (Is it that registry key?) My memory also suggests that TortoiseHg keeps its own copy of plink?
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Pageant is useful for more than just PuTTY though. I regularly use it with FileZilla, and I know it is also compatible with WinSCP (and probably more still that I don't know about).
It might be worth releasing as a standalone app, with the potential for any compatible apps to run it if it is installed.
1. Pageant is useful to other apps standalone. Maybe we could replace launching PuTTY with Pageant; you could then run PuTTY from within Pageant.
2. The usual PuTTY settings. Regarding Plink, yes, but there isn't much difference between them:
Previously known as kAlug.
Hi everybody,
Thanks a lot for the effort put into this package. I tried it today and so far it works great! So I wanted to make more people aware and have posted about it here:
https://plus.google.com/108957994038017966408/posts/P65phN6BQW2
http://selenic.com/pipermail/mercurial/2011-December/041092.html
http://sourceforge.net/mailarchive/message.php?msg_id=28504179
Keep up the good work, it's very valuable!
The QtKeysCleanup section in launcher.ini needs to be updated to Qt 4.8
Will be updated in the next release (in a few days, I believe).
Previously known as kAlug.
Aluisio, I hate to be a bother, but 2.5 is now out.
I know I've been a bit lazy to update it. I'll just wait for this month' release.
UPDATE: I'm having some issues with my custom TortoisePlink build. I want to fix it before updating.
UPDATE 2: It seems that TortoisePlink from 2.5 works (yeah, apparently I'd built a 2.5 package).
Previously known as kAlug.
2.7 was released last week, apparently. I noticed a notice in Help>About, and discovered on the site that 2.7 was released on the 3rd.
I do embedded system programming and usually have several active projects at any given time. I started using tortoisehg portable several months ago and would not want to be without it now!
From the help file: "Also available are two dockable widgets - a Repository Registry which lists all known repositories on your local machine ... "
When I first started using this app, when I opened the program I got a list of the repositories that I have been using. More recently whenever I run the program I only get a "default" in the repository registry window and need to go to file - open repository to open up an explorer window and then proceed to located the repository I want to updated. What did I break so that the list is not saved?
BTW, thanks for making this available in a portable version.
Bob
Try renaming the Data directory to something else, then start TortoiseHg Portable, add a few repositories to the registry and restart it; just to see if the repository list file is corrupt.
Previously known as kAlug.
I renamed the data directory, ran the program, added two repositories to the registry, closed and reopened the program. No luck. No repositories were shown in the registry. I am running XP on this machine. PortableApps is installed in the conventional manner on E:, an external USB hard drive.
Other than this relatively minor inconvenience, everything else seems to work just fine. Any thing else I could try? Thanks for making this program available.
BTW, when I first started using this program, entries in the repository registry were preserved. I think that stopped when I updated to 2.6 but I'm not sure. I am using 2.7 at present.
B
Can you post the contents of the Data\TortoiseHg\THG-RepoRegistry.xml file, both the original version (on the directory you renamed) and the new version (delete the new Data directory and do as before, but don't restart TortoiseHg, just close it)?
Previously known as kAlug.
In both the original (renamed) data directory and in the newly created one, the Data\TortoiseHg\ folder is empty! There was no .xml file or any other file there.
On the XP machine I have been using, I had also loaded (and forgot about) the regular, non-portable version of tortoisehg. I uninstalled that version but the problem remained. Later today, at home on a Win 7 machine, I noticed the same problem - nothing in the repository registry when I ran the program and nothing in the Data\TortoiseHg folder.
I uninstalled the 'normal' version that was also installed on the Win 7 machine and now I am saving the registry! Perhaps this is a clue?
Tomorrow I will take a look at the XP machine to see if I can find any other clues.
B
I rebooted the XP machine (evidently the uninstall of the non-portable version of tortoisehg was incomplete ?) and everything seems to be working as expected.
Apparently the portable and non-portable versions of tortoisehg don't play well together.
Aluisio, thanks for your making this program available and also for your interest in helping to solve this little mystery.
B
I spent the last two days evaluating Git, Bazaar, Mercurial, Darcs and classic SVN for my new projects. After much reading I was going choose between the three main DCVS and Mercurial had a little lead for being more Windows friendly even if Git is preeety good itself and a lot of our machine are Linux.
Then I thought what about if there was a portable version... and I find out that there are recent portable versions for both Git and Mercurial and a less recent for Bazaar.
And since I am a Fanatic user of Portable Apps the choice was at this point obvious for me... and I really kind of wanted Mercurial anyway coming from assembly, C and Python.
So thank, thank you very much.
(I worked and fix problems with registry all my life and HATE it with all my guts: one of the stupidest invention ever concocted)
... Bless the Portable Apps and Developers.
Aluisio,
When you get a chance, 2.7.1 was released March 3rd.
No hurry, works great at the moment.
2014-09-04: TortoiseHg 3.1.1 (with Mercurial 3.1.1) released
I made v3.4.2 on 'portable' installation via INNO setup (17.4mb)
https://github.com/pipiscrew/TortoiseHg-Portable/releases
you can find the the installation script attached at
https://github.com/pipiscrew/TortoiseHg-Portable/blob/master/installer.iss
Could anyone update this to the latest?
Thank You.
Hi,
how can I commit my changes? The context menu doesn't shoe me such a function.
- > Edit: Oh ok, we dont need it. Commit does not work, when only one Folder created. Solved for me. Thx for a great portable version.
Greetings
Dib
- Under Construction -