thg issueshttps://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues2020-06-21T10:33:39Zhttps://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3235Synchronize only one branch for each repository2020-06-21T10:33:39ZBitbucket ImporterSynchronize only one branch for each repository*Created originally on Bitbucket by [Rainer](https://bitbucket.org/%7Bec6407c2-5f20-45a4-8f1f-9992107a4d2f%7D/)*
*Options* in the *Synchronize* view allows to set a branch to be pushed/pulled. This works well, but if you work with more ...*Created originally on Bitbucket by [Rainer](https://bitbucket.org/%7Bec6407c2-5f20-45a4-8f1f-9992107a4d2f%7D/)*
*Options* in the *Synchronize* view allows to set a branch to be pushed/pulled. This works well, but if you work with more than one Repo the selected branch is valid for all Repos. It would be helpful if the selected branch is stored in each repository setting (.hg/hgrc).
The other way would be to select the branch by *Target*, this option can be different for each opened Repo, but if you close the Repo or TortoiseHG the *Target* Setting is lost. In this case It would be helpful if the selected *Target* is stored in each repository setting (.hg/hgrc).https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3239guess: Ability to compare copy/rename candidates2020-06-21T10:33:45ZBitbucket Importerguess: Ability to compare copy/rename candidates*Created originally on Bitbucket by [Gili](https://bitbucket.org/%7B28813353-a154-472e-a48a-a5ca553acd57%7D/)*
When reviewing copy/rename candidates, we are presented a diff window at the bottom but I would like to be able to launch ext...*Created originally on Bitbucket by [Gili](https://bitbucket.org/%7B28813353-a154-472e-a48a-a5ca553acd57%7D/)*
When reviewing copy/rename candidates, we are presented a diff window at the bottom but I would like to be able to launch external diff tools like we are able to do from the commit window.
Expected behavior: double clicking on line items in Candidate Matches window should open the default diff tool.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3248Pushing repo with subrepos is slow again2020-06-21T10:33:58ZBitbucket ImporterPushing repo with subrepos is slow again*Created originally on Bitbucket by [Zoltán Lehóczky](https://bitbucket.org/%7B5c715b88-22e2-4aec-a1d1-bb315abc09cb%7D/)*
I noticed that with the previous version TortoiseHg got much faster: before that pushing repos with many subrepos ...*Created originally on Bitbucket by [Zoltán Lehóczky](https://bitbucket.org/%7B5c715b88-22e2-4aec-a1d1-bb315abc09cb%7D/)*
I noticed that with the previous version TortoiseHg got much faster: before that pushing repos with many subrepos was slow as Tortoise went over every subrepos, even the ones not touched, and asked the server:
pushing subrepo ... to ...
searching for changes
no changes found
In the previous version this server-roundtrip was not there anymore and everything was much faster!
However with the current version 2.8.1 it seems everything is back to the slow variant. Why the change?https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3251Chunk commit not available during Amend2023-11-03T21:53:25ZBitbucket ImporterChunk commit not available during Amend*Created originally on Bitbucket by [freefaller (Tom Hartland)](https://bitbucket.org/%7B5cf4cd9e-0a95-4cc5-a5e6-d4a68da4f24a%7D/)*
When in the Commit screen and "Amend current revision" mode, it is not possible to select individual chu...*Created originally on Bitbucket by [freefaller (Tom Hartland)](https://bitbucket.org/%7B5cf4cd9e-0a95-4cc5-a5e6-d4a68da4f24a%7D/)*
When in the Commit screen and "Amend current revision" mode, it is not possible to select individual chunks (as you can when in normal "Commit changes" mode).
This means if individual chunks were selected on the original commit, it is not possible to select the same chunks when amending.
Using THG 2.8.1
Not really sure whether this is by design or it is a bug... so will set as enhancement.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3258Allow pushing deleted bookmark2020-06-21T10:34:11ZBitbucket ImporterAllow pushing deleted bookmark*Created originally on Bitbucket by [mg (Martin Geisler)](https://bitbucket.org/%7B9d06909e-8680-4a7e-ae4a-07afcfbded7e%7D/)*
When I delete a shared bookmark, TortoiseHg should make note of this and allow me to push the deletion to the ...*Created originally on Bitbucket by [mg (Martin Geisler)](https://bitbucket.org/%7B9d06909e-8680-4a7e-ae4a-07afcfbded7e%7D/)*
When I delete a shared bookmark, TortoiseHg should make note of this and allow me to push the deletion to the server.
On the command line you run
$ hg bookmark -d foo
$ hg push -B foo
to delete a bookmark from the server. As far as I can see, there is no equivalent in current TortoiseHg.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3279"Nonetype has no attribute readline" when changing repo port2020-06-21T10:34:35ZBitbucket Importer"Nonetype has no attribute readline" when changing repo port*Created originally on Bitbucket by [ekolis (Ed Kolis)](https://bitbucket.org/%7B952af717-5772-4ff3-9551-eb66749b1c88%7D/)*
One of the repos I'm using changed its port from 65001 to 3690 without changing the rest of its URL. I changed t...*Created originally on Bitbucket by [ekolis (Ed Kolis)](https://bitbucket.org/%7B952af717-5772-4ff3-9551-eb66749b1c88%7D/)*
One of the repos I'm using changed its port from 65001 to 3690 without changing the rest of its URL. I changed that in TortoiseHG so I could continue using the repo, but now I get this error whenever I try to pull from it.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3301searching text containing square brackets fails, need to be escaped2020-06-21T10:35:03ZBitbucket Importersearching text containing square brackets fails, need to be escaped*Created originally on Bitbucket by [dshor](https://bitbucket.org/%7Bd2017688-9525-4c7b-aab7-d04bcc7dc1d1%7D/)*
looking for `array[1]` in the history window fails, it need to be escaped to `array\[1\]`
kind of confusing in some cases....*Created originally on Bitbucket by [dshor](https://bitbucket.org/%7Bd2017688-9525-4c7b-aab7-d04bcc7dc1d1%7D/)*
looking for `array[1]` in the history window fails, it need to be escaped to `array\[1\]`
kind of confusing in some cases...
maybe to do the regexp and plain text search in that case ?https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3308Green activity bar2020-06-21T10:35:10ZBitbucket ImporterGreen activity bar*Created originally on Bitbucket by [tambia (Tambi Ashmoz)](https://bitbucket.org/%7Ba1b7f8a2-e74c-4a9a-b45c-8f11dc580806%7D/)*
Please make a different workaround for hiding the green activity bar, it is very annoying.
the suggested ...*Created originally on Bitbucket by [tambia (Tambi Ashmoz)](https://bitbucket.org/%7Ba1b7f8a2-e74c-4a9a-b45c-8f11dc580806%7D/)*
Please make a different workaround for hiding the green activity bar, it is very annoying.
the suggested workaround is not convenient, pressing on the screen causing selecting other items.
you can fix this by making whole area of the green activity bar press-able (rather than pointing only on the 'x' button on it AND you can make it hide after some timeout (like messages in WAZE)
of course with setting like timeout length and if should hide also red (failures) activity bars.
Thankshttps://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3316Araxis Merge: File always marked as resolved2020-06-21T10:35:22ZBitbucket ImporterAraxis Merge: File always marked as resolved*Created originally on Bitbucket by Anonymous*
When I merge a file using Araxis Merge as my merge tool, the file is always marked as resolved even though I don't save the result in Araxis Merge.*Created originally on Bitbucket by Anonymous*
When I merge a file using Araxis Merge as my merge tool, the file is always marked as resolved even though I don't save the result in Araxis Merge.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3319Per-line chunk selection2020-06-21T10:35:25ZBitbucket ImporterPer-line chunk selection*Created originally on Bitbucket by Anonymous*
I would really appreciate the ability to select individual lines, rather than "chunks" when partially committing a file.
In the file I'm about to commit, I've got two logically separate ...*Created originally on Bitbucket by Anonymous*
I would really appreciate the ability to select individual lines, rather than "chunks" when partially committing a file.
In the file I'm about to commit, I've got two logically separate features (one of which is incomplete), but which are side-by-side in the source code and I can't separate them within the chunk selector. (I should have checked in the code before starting the second feature, but I forgot.)
If I could have a line-by-line chunk selection mechanism, that would be very handy.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3340Block "undo" if last revision pushed2020-06-21T10:35:53ZBitbucket ImporterBlock "undo" if last revision pushed*Created originally on Bitbucket by [freefaller (Tom Hartland)](https://bitbucket.org/%7B5cf4cd9e-0a95-4cc5-a5e6-d4a68da4f24a%7D/)*
Can I suggest that the "undo" feature is disabled if the last revision has been pushed?
I've been in ...*Created originally on Bitbucket by [freefaller (Tom Hartland)](https://bitbucket.org/%7B5cf4cd9e-0a95-4cc5-a5e6-d4a68da4f24a%7D/)*
Can I suggest that the "undo" feature is disabled if the last revision has been pushed?
I've been in the position several times where I have (completely self-induced) been a complete idiot by doing the following actions...
- Commit a change
- Push change to remote server
- Some time later notice something, so "undo" the last change
- Recommit the change
- Push change to remote server to be reminded that I'm an idiot, and that this is going to cause two branch heads.
Blocking the "undo" would (hopefully) stop me being such a complete idiot - at least where this is concerned.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3342Fold patches should check for local changes first2020-06-21T10:35:55ZBitbucket ImporterFold patches should check for local changes first*Created originally on Bitbucket by Anonymous*
Currently, it's like this:
1) From the workbench, I right click on a patch and select "Fold patches..."
2) A dialog appears where I edit a new patch message
3) I click OK and either the ...*Created originally on Bitbucket by Anonymous*
Currently, it's like this:
1) From the workbench, I right click on a patch and select "Fold patches..."
2) A dialog appears where I edit a new patch message
3) I click OK and either the patches are folded successfully, OR it fails because there are local changes in my working directory. In that case I lose the new patch message.
It would be nicer like if I either was immediately informed about the local changes before I start editing the new patch message, OR if I the dialog stayed open (non-modal) so I can refresh/cleanup my local state and retry the folding without losing the new patch message.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3345Paths listed in projrc not appearing in Synchronize widget2020-06-21T10:35:58ZBitbucket ImporterPaths listed in projrc not appearing in Synchronize widget*Created originally on Bitbucket by [muse_ee (Brian Bubnash)](https://bitbucket.org/%7B376b721e-ba35-4165-9f15-3a05f20c68b3%7D/)*
A remote repository location defined in the [paths] section of my projrc file is not visible when using th...*Created originally on Bitbucket by [muse_ee (Brian Bubnash)](https://bitbucket.org/%7B376b721e-ba35-4165-9f15-3a05f20c68b3%7D/)*
A remote repository location defined in the [paths] section of my projrc file is not visible when using the Synchronize widget in THG Workbench to synchronize repositories. Call this repository "server". I can go into the Windows terminal and run "hg incoming server" and the command works fine, so I know that the setting is visible to the underlying hg installation. I also know that TortoiseHg knows that projrc is enabled for this project, because when I go into TortoiseHg Settings for my repository I see a tab for project settings (.hg/projrc). Therefore I'm pretty sure this is just a bug or quirk of the TortoiseHg GUI where it is not looking at the paths in projrc when displaying available aliases. https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3364Merge Conflict !!2020-06-21T10:36:21ZBitbucket ImporterMerge Conflict !!*Created originally on Bitbucket by [Faruk Aydoğan](https://bitbucket.org/%7Bb494fa2e-b889-4ebf-9c8d-bea45da81aa9%7D/)*
I am developing my project from two different computers and I have repo on bitbucket. I push my repo three ours ago ...*Created originally on Bitbucket by [Faruk Aydoğan](https://bitbucket.org/%7Bb494fa2e-b889-4ebf-9c8d-bea45da81aa9%7D/)*
I am developing my project from two different computers and I have repo on bitbucket. I push my repo three ours ago from my computer. And three ours later I can not pull my changes, I get this error and I have no idea to fix it:
An error occurred. Detailed message: An error was raised by libgit2. Category = Checkout (MergeConflict).
15 conflicts prevent checkout
Is there anyone can help me please.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3366Web Server does not remember last config file2020-06-21T10:36:23ZBitbucket ImporterWeb Server does not remember last config file*Created originally on Bitbucket by [Marcin Wisnicki](https://bitbucket.org/%7B37f087db-a5b5-40eb-ab3b-83b9b2c2134f%7D/)*
There is a drop down for config file but it's empty.
Also, it should start with last config file used in curren...*Created originally on Bitbucket by [Marcin Wisnicki](https://bitbucket.org/%7B37f087db-a5b5-40eb-ab3b-83b9b2c2134f%7D/)*
There is a drop down for config file but it's empty.
Also, it should start with last config file used in current repository by default.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3381Locked folders/files on Windows (again)2020-06-21T10:36:42ZBitbucket ImporterLocked folders/files on Windows (again)*Created originally on Bitbucket by [schlamar (Marc Schlaich)](https://bitbucket.org/%7B0ed8ebc9-2100-466d-9d4d-dbd5d2caed79%7D/)*
I'm seeing again the issues reported in #1783, this is probably a regression from the workaround in 1a5ee...*Created originally on Bitbucket by [schlamar (Marc Schlaich)](https://bitbucket.org/%7B0ed8ebc9-2100-466d-9d4d-dbd5d2caed79%7D/)*
I'm seeing again the issues reported in #1783, this is probably a regression from the workaround in 1a5ee1cd1490 (see #3298).https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3390shellext: Windows freeze at login when network drives are unreachable2020-06-21T10:36:54ZBitbucket Importershellext: Windows freeze at login when network drives are unreachable*Created originally on Bitbucket by [leriton (LeRiton)](https://bitbucket.org/%7B245d8a4d-0afc-4ff5-b2c5-9fd1c7c16ca8%7D/)*
Hi guys,
I'm experiencing the exact same problem as mentioned here : http://selenic.com/pipermail/mercurial/2...*Created originally on Bitbucket by [leriton (LeRiton)](https://bitbucket.org/%7B245d8a4d-0afc-4ff5-b2c5-9fd1c7c16ca8%7D/)*
Hi guys,
I'm experiencing the exact same problem as mentioned here : http://selenic.com/pipermail/mercurial/2008-August/020505.html
*"I think I found the problem. The PC I am using is a work laptop I just
got and I realized hat IT placed my home directory on a network drive.
Tortoise places its configuration information information on the home
drive, which is then unreachable when the PC is not connected on the
network. So when I boot the PC, log in and open a Windows Explorer
sesion, TortoiseHg must be trying o read its config files which are
nreachale, causing the massive slowdown in the Explorer. As soon as I
get back to work Ill change my home drive to be positionned in a local
disk to solve the problem."*
In this case, Windows is freezing (nothing on the screen) during 10 minutes after login, laptop is unusable.
All users of this laptop are facing the issue, even if they don't own Mercurial repositories on their network drives (even if they don't use Mercurial at all).
Is there any way to make TortoiseHg less dependent of network drives? Maybe overriding a path option?
TortoiseHG is 2.9.1, Windows XP
Any help appreciated, cheershttps://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3391Add ability to have rules that will disallow the merging of one branch to ano...2020-06-21T10:36:56ZBitbucket ImporterAdd ability to have rules that will disallow the merging of one branch to another.*Created originally on Bitbucket by [dsargent](https://bitbucket.org/%7B5b8b203a-3be5-4427-9513-b41a8027fb42%7D/)*
We have a pretty typical setup:
* trunk
* test
* stage
* dev
We never allow (want) a developer to merge dev, stage o...*Created originally on Bitbucket by [dsargent](https://bitbucket.org/%7B5b8b203a-3be5-4427-9513-b41a8027fb42%7D/)*
We have a pretty typical setup:
* trunk
* test
* stage
* dev
We never allow (want) a developer to merge dev, stage or test into trunk but they should be merging trunk into the other three. Unfortunately, sometimes mistakes happen (especially with those new to source control) and then we have to back changes out.
We'd love a feature that would tell Tortoise to never let a dev merge branch X into branch Y
I understand this would probably have to be a per user setting but anything is better than nothing.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3397Frequent crash when app is closed (Windows 7 32 bit)2020-06-21T10:37:08ZBitbucket ImporterFrequent crash when app is closed (Windows 7 32 bit)*Created originally on Bitbucket by [pavangayakwad (pavangayakwad NA)](https://bitbucket.org/%7B90de24bd-0d23-43d0-b755-b1056df487ca%7D/)*
Steps:
- Create a folder in windows explorer
- Right click on folder and chose context menu "To...*Created originally on Bitbucket by [pavangayakwad (pavangayakwad NA)](https://bitbucket.org/%7B90de24bd-0d23-43d0-b755-b1056df487ca%7D/)*
Steps:
- Create a folder in windows explorer
- Right click on folder and chose context menu "TortiseHg" -> Clone
- now close the "Clone" window and gets a crash report.
Environment
Windows 7 32 bit with SP1, Lenovo laptop.
*Attachments:* [Crash](/uploads/7f00026798a79d7cecf51a777b66cde5/Crash.png)https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/3413Crashes often result in "Not a head revision" [Workaround included]2020-06-21T10:37:26ZBitbucket ImporterCrashes often result in "Not a head revision" [Workaround included]*Created originally on Bitbucket by [FlorianGeorge](https://bitbucket.org/%7B875a738f-e7aa-4e6e-9709-32892f102675%7D/)*
I am using a repository on an encrypted volume (V:) which is sitting on an external USB SSD (W:).
Whenever someth...*Created originally on Bitbucket by [FlorianGeorge](https://bitbucket.org/%7B875a738f-e7aa-4e6e-9709-32892f102675%7D/)*
I am using a repository on an encrypted volume (V:) which is sitting on an external USB SSD (W:).
Whenever something goes wrong with the mounted partition (e.g. the cable was disconnected for a millisecond, or the I/O driver had a hiccup), 99% of the Applications accessing the volume are able to continue working properly, worst case they crash, but no data is lost.
However, usually when this happens, my repository gets slightly corrupted. I am not sure whether tortoiseHg Workbench has to be openend at the time it occurs, or whether it is enough that the TortoiseHG Overlay Icon Service is running in the background.
The symptom for this corruption is the "Not a head revision" message in the TortoiseHg Workbench, looking like this (not my own screenshot):
![Not a head revision](http://i.stack.imgur.com/Kde0i.jpg)
A 100% working fix for this situation is running
~~~
hg debugrebuildstate -r tip
~~~
if I am currently working on the tip revision or
~~~
hg debugrebuildstate -r 20939
~~~
if 20939 was my active revision before the corruption occurred.
I am happy that I am always able to resume working quickly after a repository corruption like this happened, but I am curious whether it is possible to reduce the chances of it happening in the future.
I appears to me that the file /.hg/dirstate is the source of the situation. In certain intervals, I am observing a second file, e.g. dirstate-c353d00c, appearing and quickly disappearing. I assume that this means that the dirstate gets updated at that time, and if something goes wrong during that operation, my repository gets corrupted, but only the flag for the revision that's active is affected, nothing else gets lost.
Could the process of updating the dirstate be modified to prevent the kind of corruption I am experiencing from occuring?