thg issueshttps://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues2020-06-21T11:10:23Zhttps://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4976TortoiseHg 4.4.1 - Terminal shortcut broken in this release2020-06-21T11:10:23ZBitbucket ImporterTortoiseHg 4.4.1 - Terminal shortcut broken in this release*Created originally on Bitbucket by [nghing (Nghi Nguyen)](https://bitbucket.org/%7B33303570-7cda-4d16-a591-3003d8cce14a%7D/)*
the Terminal shortcut (when right-click on a Repository) supposed to launch the Windows cmd but is no longer ...*Created originally on Bitbucket by [nghing (Nghi Nguyen)](https://bitbucket.org/%7B33303570-7cda-4d16-a591-3003d8cce14a%7D/)*
the Terminal shortcut (when right-click on a Repository) supposed to launch the Windows cmd but is no longer working. Back-install 4.3.1 works, so definitely a regression in the new 4.4.1 release.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4974meld-auto meld-noauto2020-06-21T11:10:21ZBitbucket Importermeld-auto meld-noauto*Created originally on Bitbucket by [daschuer](https://bitbucket.org/%7B11ead6d3-bf71-4a9c-9a28-88d8bda3028c%7D/)*
Like kdiff3 TortoiseHG should support both option for meld
Here is my meld settings for auto merge:
[merge-tools]
...*Created originally on Bitbucket by [daschuer](https://bitbucket.org/%7B11ead6d3-bf71-4a9c-9a28-88d8bda3028c%7D/)*
Like kdiff3 TortoiseHG should support both option for meld
Here is my meld settings for auto merge:
[merge-tools]
meld-auto.regkey=SOFTWARE\Meld
meld-auto.regkeyalt=SOFTWARE\Wow6432Node\Meld
meld-auto.regname=Executable
meld-auto.gui=True
meld-auto.priority=-2
meld-auto.args=$local $base $other --auto-merge -o $output
meld-auto.checkchanged=True
meld-auto.diffargs=-a --label='$plabel1' $parent --label='$clabel' $child
meld-auto.diff3args=-a --label='$plabel1' $parent1 --label='$clabel' $child --label='$plabel2' $parent2
meld-auto.dirdiff=True
This should also be considered together with Issue #4973
Auto should use the merge tool merging features. nonauto should allow to continue a mercurial merged file.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4971Incorrect 'Outgoing' lists if log command is aliased2020-06-21T11:10:17ZBitbucket ImporterIncorrect 'Outgoing' lists if log command is aliased*Created originally on Bitbucket by [DaveInCaz (David Hollman)](https://bitbucket.org/%7B2dd8bec0-e2b4-43d0-b274-6ee79db66b75%7D/)*
When I click the outgoing button on the main toolbar THG shows me a list of any draft changesets which D...*Created originally on Bitbucket by [DaveInCaz (David Hollman)](https://bitbucket.org/%7B2dd8bec0-e2b4-43d0-b274-6ee79db66b75%7D/)*
When I click the outgoing button on the main toolbar THG shows me a list of any draft changesets which DO need to be pushed, but then it follows that with apparently all the public changesets which are already synchronized. Confusing.
The second set should not be shown.
Note - I believe this is the same whether I use the main toolbar or the smaller toolbar in sync view.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4960hyst entry view: ancestrs list too long2020-06-21T11:10:05ZBitbucket Importerhyst entry view: ancestrs list too long*Created originally on Bitbucket by [Alex Rayne (Александр Литягин)](https://bitbucket.org/%7Ba08cf82d-1da1-46f4-8019-7f030383d366%7D/)*
Hallow!
In my situation, master head have many ancestors bookmarks. so in log entr vies, this ance...*Created originally on Bitbucket by [Alex Rayne (Александр Литягин)](https://bitbucket.org/%7Ba08cf82d-1da1-46f4-8019-7f030383d366%7D/)*
Hallow!
In my situation, master head have many ancestors bookmarks. so in log entr vies, this ancestors lists with looong list, and make ocupy most part of screen.
like this:
![thg-issue-logview.png](https://bitbucket.org/repo/48R4X/images/2072759121-thg-issue-logview.png)https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4958Pinning the tortoisehg shortcut to the windows10 taskbar results in a blank icon2020-06-21T11:10:01ZBitbucket ImporterPinning the tortoisehg shortcut to the windows10 taskbar results in a blank icon*Created originally on Bitbucket by [pwilliams (Pete Williams)](https://bitbucket.org/%7B1c044d3f-9048-41b2-95da-36d34159bf45%7D/)*
On install, when i run workbench if i pin the icon to the taskbar the turtle disappears and i only see a...*Created originally on Bitbucket by [pwilliams (Pete Williams)](https://bitbucket.org/%7B1c044d3f-9048-41b2-95da-36d34159bf45%7D/)*
On install, when i run workbench if i pin the icon to the taskbar the turtle disappears and i only see a blank white page icon. I am unable to change the icon/shortcut in the shortcut properties because it doesn't appear to target an actual file.
*Attachments:* [screenshot](/uploads/509f7d690d3c37454f02bb32ca69721c/screenshot.PNG)https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4957Improve rebase dialog: Use phase to swap source / destination etc.2020-06-21T11:09:59ZBitbucket ImporterImprove rebase dialog: Use phase to swap source / destination etc.*Created originally on Bitbucket by Anonymous*
In `RepoWidget` `rebaseDlg` two selected revisions are used as source and destination of the rebase operation: `{'source': self.menuselection[0], 'dest': self.menuselection[1]}`.
For som...*Created originally on Bitbucket by Anonymous*
In `RepoWidget` `rebaseDlg` two selected revisions are used as source and destination of the rebase operation: `{'source': self.menuselection[0], 'dest': self.menuselection[1]}`.
For some reason this order is always counter-intuitive to me. To me it seems more natural to click the destination first and then right-click the source to open the context menu and execute the rebase command on the source revision.
But I guess just swapping them would confuse users that are now used to this behavior.
I'm very thankful that there is a "Swap source and destination" link/button that can easily fix the problem, if it is noticed. Unfortunately the UI makes it more difficult than necessary to notice the problem: There is a lot of information, but not necessarily all of it is useful and not all useful information is shown.
The phase (secret / draft / public) of the two changesets is missing. When source is public and destination is draft, I probably mixed them up and want to swap them. This could IMO even be done automatically as a heuristic.
To me branch and tag and date are just distracting.
The bold labels are also quite distracting.
More helpful would be "author coloring", but that is missing.
(The source changeset title is missing the word "source".)
The source and destination groupboxes are stacked vertically. It would be much more helpful to stack them horizontally, so the respective fields are next to each other.
Bonus: Show some hints (i.e. colored "source" and "destination" annotations, or an maybe even an arrow from source to destination?) in the workbench graph on the selected changesets themselves.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4949Add menu entries and keyboard shortcuts for Commit panel actions: Commit chan...2020-06-21T11:09:48ZBitbucket ImporterAdd menu entries and keyboard shortcuts for Commit panel actions: Commit changes, Amend current revision, Create a new patch, Refresh current patch*Created originally on Bitbucket by [thomasdd (Thomas D.)](https://bitbucket.org/%7B8da0c5d2-9d85-454e-8331-a0535f3a8cc6%7D/)*
When the Commit panel is shown, it's main actions are not keyboard-accessible at all. Which violates accessib...*Created originally on Bitbucket by [thomasdd (Thomas D.)](https://bitbucket.org/%7B8da0c5d2-9d85-454e-8331-a0535f3a8cc6%7D/)*
When the Commit panel is shown, it's main actions are not keyboard-accessible at all. Which violates accessibility guidelines, and is also very inconvenient because those actions are very frequent, especially "Refresh current patch".
Please add the following menus to the main Repository menu (maybe after "Unbundle" command):
* Commit changes
* Amend current revision
* Create a new patch
* Refresh current patch
If you don't like 4 first-level entries, create one first-level entry "Commit >", then those 4 entries in the submenu.
Menus are just for completeness sake, but more importantly, users would benefit from having dedicated keyboard shortcuts for these pretty frequent actions:
Proposal for keyboard shortcuts:
* Commit changes (Ctrl+Shift+C)
* Amend current revision (Ctrl+Shift+M; because Ctrl+Shift+A is 'Load All Revisions')
* Create a new patch (Ctrl+Shift+P; because Ctrl+Shift+C proposed for 'Commit' and Ctrl+Shift+N is 'Clone Repository')
* Refresh current patch (Ctrl+Shift+R)https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4947Add missing commands to patch queue context menu, and make patch context menu...2020-06-21T11:09:45ZBitbucket ImporterAdd missing commands to patch queue context menu, and make patch context menus of queue widget and repository list the same*Created originally on Bitbucket by [thomasdd (Thomas D.)](https://bitbucket.org/%7B8da0c5d2-9d85-454e-8331-a0535f3a8cc6%7D/)*
For users of the patch queue widget, some patch commands are not easy to discover simply because they are not...*Created originally on Bitbucket by [thomasdd (Thomas D.)](https://bitbucket.org/%7B8da0c5d2-9d85-454e-8331-a0535f3a8cc6%7D/)*
For users of the patch queue widget, some patch commands are not easy to discover simply because they are not found on the patch queue context menu, which would appear to be the most logical place for patch commands... E.g. I remember searching for "Fold patches" in vain because I just assumed that all patch commands would be found in the patch queue widget. It was only through google that I found out there's another, surprisingly *different* patch context menu on patches in the repository list.
STR
1. Right-click on patch queue
2. Look for "Apply patch" (which should be relabeled to "Apply up to this patch", see #4946)
3. Try to "Apply only this patch"
4. Try to "Fold patches..."
5. Try to "Shelve..." patches or chunks thereof
Actual result
- important, everyday patch commands are NOT available from patch queue context
- command labels differ between context menu of patch queue widget and patches context menu in repository list - it's not immediately obvious that "Go to patch" is the same as "Apply patch", and "Apply patch" isn't very clear in itself...
Expected result
1. command labeling should be consistent everyhwere
* relabel "Go to patch" (from queue) and "Apply patch" (from list) to "Apply up this patch"
2. All patch commands should be available from patch queue context (proposed additions marked with *, see below)
3. The context menu of patches in the queue widget and in the repository list should be the same (see below)
4. Separators should be added to mark logical groups of commands (see below)
* first group: commands that apply to the selected and right-clicked patch
* second group: patch management commands (rename/fold/shelve/delete)
* third group: commands that apply to the patch queue, NOT the selected and right-clicked patch
* fourth group: MQ options
5. Proposed uniform patch context menu for queue widget AND repository list:
- Apply up to this patch (currently labeled "Go to this patch")
- Apply onto original parent*
- Apply only this patch*
- Set guards...
- Finish patch (Shouldn't that be "Commit patch"?)
-----------------------------------------
- Rename patch...
- Fold patches...*
- Shelve...*
- Delete patches...
-----------------------------------------
- Apply one patch* (should be "Apply next patch")
- Apply all patches*
- Unapply one patch* (should be "Unapply top patch")
- Unapply all patches*
-----------------------------------------
- MQ options...*https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4946In context menu of patches in repository list, improve wording of "Apply patc...2020-06-21T11:09:44ZBitbucket ImporterIn context menu of patches in repository list, improve wording of "Apply patch" command*Created originally on Bitbucket by [thomasdd (Thomas D.)](https://bitbucket.org/%7B8da0c5d2-9d85-454e-8331-a0535f3a8cc6%7D/)*
The current wording of patch commands in the context menu of patches in repository list is not very clear. "A...*Created originally on Bitbucket by [thomasdd (Thomas D.)](https://bitbucket.org/%7B8da0c5d2-9d85-454e-8331-a0535f3a8cc6%7D/)*
The current wording of patch commands in the context menu of patches in repository list is not very clear. "Apply patch" can easily be misunderstood as "Apply only this patch" but it really means "Apply (all patches) up to this patch".
STR
1. right-click on patch in repository list
2. try to figure out the exact meaning of "Apply patch"
Actual Result:
1. "Apply patch" might be misunderstood as "Apply *only this patch*"
Expected result:
1. "Apply patches up to this patch" (or maybe "Apply all up to this patch" or even just "Apply up to this patch")
[Edited: Sorry, there were some misunderstandings on my side in the first version of this issue]https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4940wiki: Misleading macOS installation instructions for MacPorts2020-06-21T11:09:36ZBitbucket Importerwiki: Misleading macOS installation instructions for MacPorts*Created originally on Bitbucket by Anonymous*
Referring to [these wiki instructions](https://bitbucket.org/tortoisehg/thg/wiki/developers/MacOSX#!install-via-macports)
The part "*Installing TortoiseHg this way usually takes a couple...*Created originally on Bitbucket by Anonymous*
Referring to [these wiki instructions](https://bitbucket.org/tortoisehg/thg/wiki/developers/MacOSX#!install-via-macports)
The part "*Installing TortoiseHg this way usually takes a couple of hours because Qt is compiled from its sources.*" is no longer true unless there are certain circumstances (like the user picking some weird configuration or non-standard path, using a pre-released OS etc.) Qt is usually installed from binary sources, so the installation should generally be quick.
But more importantly, the build instructions should boil down to
```
#!bash
sudo port install tortoisehg
```
and then everything should work out of the box. I see no reason for the user to manually install tortoise unless there's a need for the super latest and greatest features or for actual development.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4939need coloring graph for bookmarks branches2020-06-21T11:09:35ZBitbucket Importerneed coloring graph for bookmarks branches*Created originally on Bitbucket by [Alex Rayne (Александр Литягин)](https://bitbucket.org/%7Ba08cf82d-1da1-46f4-8019-7f030383d366%7D/)*
Hallow!
Git workflow style need havily use bookmarks vs named branches. So, at present, this bookm...*Created originally on Bitbucket by [Alex Rayne (Александр Литягин)](https://bitbucket.org/%7Ba08cf82d-1da1-46f4-8019-7f030383d366%7D/)*
Hallow!
Git workflow style need havily use bookmarks vs named branches. So, at present, this bookmaked branches are in single color.
it would be very helpful to color this bookmarks. this can solve #4938
no-named branches would be more distinguisheble if it have differ colour saturation or linestyle.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4934COPYING.txt not installed by setup.py on POSIX2020-06-21T11:09:26ZBitbucket ImporterCOPYING.txt not installed by setup.py on POSIX*Created originally on Bitbucket by Anonymous*
This happened with Nix package manager.
It installs thg like this:
```
python setup.py install --prefix=$out
```
But this doesn't create `$out/share/doc/tortoisehg/Copying.tx...*Created originally on Bitbucket by Anonymous*
This happened with Nix package manager.
It installs thg like this:
```
python setup.py install --prefix=$out
```
But this doesn't create `$out/share/doc/tortoisehg/Copying.txt.gz` which should provide license. Adding lines
```
mkdir -p $out/share/doc/tortoisehg
cp COPYING.txt $out/share/doc/tortoisehg/Copying.txt.gz
```
to build instructions fixes the issue, but maybe that should be embedded to setup.py?https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4932Missing working directory / current path case normalization on Windows2020-06-21T11:09:24ZBitbucket ImporterMissing working directory / current path case normalization on Windows*Created originally on Bitbucket by [psuter (Peter Suter)](https://bitbucket.org/%7B48b289e8-68dd-4aa4-8d3a-6458c5363d69%7D/)*
On Windows paths are case preserving but case insensitive.
```
C:\>md A
C:\>cd a
C:\A>hginit .
C:\A>md...*Created originally on Bitbucket by [psuter (Peter Suter)](https://bitbucket.org/%7B48b289e8-68dd-4aa4-8d3a-6458c5363d69%7D/)*
On Windows paths are case preserving but case insensitive.
```
C:\>md A
C:\>cd a
C:\A>hginit .
C:\A>md B
C:\A>cd b
C:\A\B>echo foo>file.txt
C:\A\B>hg add file.txt
C:\A\B>cd ..
C:\A>hg commit -m "Added file"
C:\A>thg filelog b\file.txt
C:\A>thg filelog B\file.txt
```
The last command (`thg filelog B\file.txt`) works. The previous command (`thg filelog b\file.txt`) does not work. There is no error message, but no changesets are shown.
Worse:
1. Press WIN+R, write `c:\a\b`. (Windows Explorer opens in `c:\a\b`.)
2. Right click `file.txt` and *TortoiseHG* and *Revision History*. (Again, this does not work!)
3. Press CTRL+L (Focus on the location bar)
4. Write `cmd.exe` and hit ENTER. (Command shell opens in `c:\a\b>`.)
5. `c:\a\b>thg filelog file.txt` (Again, this does not work!)
In these cases the user that performed step 2. or step 5. did nothing wrong and can not really do anything to fix the problem. In reality this may happen much later than the "problematic"[^1] step 1. and the path may be much longer and less obvious than in this simple example. A single "wrong"[^2] lowercase character anywhere in the current path can lead to much confusion.
Please consider if on Windows normalizing (some) paths would be possible.
Thanks!
[^1]: On Windows of course this is actually not usually considered problematic.
[^2]: On Windows of course this is actually not usually considered wrong.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4931Putting a fileset into the file filter editbox causes a stracktrace2020-06-21T11:09:23ZMatt HarbisonPutting a fileset into the file filter editbox causes a stracktraceI started typing "set:", and it was OK. For each subsequent letter, it popped open the crash dialog. After I got the closing parenthesis in, it was OK and filtered properly. My repo is on the E: drive; I'm not sure why it also referen...I started typing "set:", and it was OK. For each subsequent letter, it popped open the crash dialog. After I got the closing parenthesis in, it was OK and filtered properly. My repo is on the E: drive; I'm not sure why it also references C:\. For the record, I was typing 'set:exec()'.
I haven't looked into this at all, but I'm guessing a simple work around is to not keep calling match.match() once the 'set:' prefix is typed, until the last parenthesis is typed.
```
#!python
** Mercurial version (4.3.1). TortoiseHg version (4.3.1)
** Command: --nofork workbench
** CWD: C:\Users\mharbison.MATT7H-PC\Desktop
** Encoding: UTF-8
** Extensions loaded: purge, schemes, evolve, strip, mq, rebase, eol, extdiff, mercurial_keyring, largefiles
** Python version: 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]
** Windows version: sys.getwindowsversion(major=6, minor=1, build=7600, platform=2, service_pack='')
** Processor architecture: x86
** Qt-4.8.7 PyQt-4.11.4 QScintilla-2.9
Traceback (most recent call last):
File "tortoisehg\hgqt\revdetails.pyo", line 408, in _applyFileNameFilter
File "tortoisehg\hgqt\manifestmodel.pyo", line 300, in setNameFilter
File "tortoisehg\hgqt\manifestmodel.pyo", line 378, in _repopulateNodes
File "tortoisehg\hgqt\manifestmodel.pyo", line 405, in _populateNodes
File "tortoisehg\hgqt\manifestmodel.pyo", line 526, in _makematcher
File "mercurial\match.pyo", line 153, in match
File "mercurial\match.pyo", line 381, in __init__
File "mercurial\match.pyo", line 826, in _buildmatch
File "mercurial\match.pyo", line 43, in _expandsets
File "mercurial\context.pyo", line 196, in getfileset
File "mercurial\fileset.pyo", line 592, in getfileset
File "mercurial\fileset.pyo", line 110, in getset
File "mercurial\fileset.pyo", line 113, in stringset
File "mercurial\fileset.pyo", line 534, in matcher
File "mercurial\context.pyo", line 306, in match
File "mercurial\match.pyo", line 148, in match
File "mercurial\match.pyo", line 194, in _donormalize
File "mercurial\pathutil.pyo", line 188, in canonpath
File "ntpath.pyo", line 529, in relpath
ValueError: path is on drive E:, start on drive C:
```https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4930Linux developers wiki page does not say that the `mercurial` python module is...2020-06-21T11:09:22ZBitbucket ImporterLinux developers wiki page does not say that the `mercurial` python module is needed*Created originally on Bitbucket by [Russell Warren](https://bitbucket.org/%7B5e8ff0c5-ce8b-4c99-ae36-9bc70ededd3e%7D/)*
This wiki page:
https://bitbucket.org/tortoisehg/thg/wiki/developers/Linux
does not indicate that the `mercur...*Created originally on Bitbucket by [Russell Warren](https://bitbucket.org/%7B5e8ff0c5-ce8b-4c99-ae36-9bc70ededd3e%7D/)*
This wiki page:
https://bitbucket.org/tortoisehg/thg/wiki/developers/Linux
does not indicate that the `mercurial` python module is needed. History, and an example of the resulting failure (due to an old version of this module) are in this issue:
https://bitbucket.org/tortoisehg/thg/issues/4929/module-object-has-no-attribute-command-onhttps://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4927bookmark activation from book marksmenu2020-06-21T11:09:19ZBitbucket Importerbookmark activation from book marksmenu*Created originally on Bitbucket by [Alex Rayne (Александр Литягин)](https://bitbucket.org/%7Ba08cf82d-1da1-46f4-8019-7f030383d366%7D/)*
Hallow!
bookmarks dialog now can`t activate existing bookmark. if i alredy updated on revision tha...*Created originally on Bitbucket by [Alex Rayne (Александр Литягин)](https://bitbucket.org/%7Ba08cf82d-1da1-46f4-8019-7f030383d366%7D/)*
Hallow!
bookmarks dialog now can`t activate existing bookmark. if i alredy updated on revision that have wanted inactive bookmark, there is no way to activate it.
imho, there is can be added one more button "activate"/"deactivate" in bokmarks dialog.
update dialog can be used to activate anted bookmark. but, nativaly, when i try to manipulate with boomarks, i go to bookmark`s dialog. Update - not obvious way to activate it, when right mouse menu have "bookmarks" item.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4925Add "32-bit/64-bit" to version information in "About TortoiseHg"2020-06-21T11:09:17ZBitbucket ImporterAdd "32-bit/64-bit" to version information in "About TortoiseHg"*Created originally on Bitbucket by [thomasdd (Thomas D.)](https://bitbucket.org/%7B8da0c5d2-9d85-454e-8331-a0535f3a8cc6%7D/)*
STR
1. From "About TortoiseHg" dialogue, try to find out if you're running 32-bit version or 64-bit versio...*Created originally on Bitbucket by [thomasdd (Thomas D.)](https://bitbucket.org/%7B8da0c5d2-9d85-454e-8331-a0535f3a8cc6%7D/)*
STR
1. From "About TortoiseHg" dialogue, try to find out if you're running 32-bit version or 64-bit version of TortoiseHg
Actual result
1. No information about 32-bit vs. 64-bit in the "About TortoiseHg" dialogue.
Expected result
1. Add 32-bit/64-bit to the version string, like this:
version 4.3.1 (32-bit)
version 4.3.1 (64-bit)
That would be helpful.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4924mq: Add "Edit Patch File" and "Explore Patch Queue" to patch context menu2020-06-21T11:09:16ZBitbucket Importermq: Add "Edit Patch File" and "Explore Patch Queue" to patch context menu*Created originally on Bitbucket by [thomasdd (Thomas D.)](https://bitbucket.org/%7B8da0c5d2-9d85-454e-8331-a0535f3a8cc6%7D/)*
User story:
I work with patches a lot. Before posting my patches to the public bug tracker, I often want t...*Created originally on Bitbucket by [thomasdd (Thomas D.)](https://bitbucket.org/%7B8da0c5d2-9d85-454e-8331-a0535f3a8cc6%7D/)*
User story:
I work with patches a lot. Before posting my patches to the public bug tracker, I often want to verify the actual patch file created by thg, which is a fast and efficient way of double-checking for errors and reviewing your changes en block. The patch is right in front of me, but there's no easy way to edit it from inside thg as can be done with other source files ("Edit Local"), so I have to search for the patch again using Windows Explorer.
I also often have the need to create backup copies of patch files before refreshing them, and more generally, to manage patch files. Again, the patch files are right in front of me, and thg knows their location, but there's no way from inside thg to access the folder location of the patch queue as can be done with other source files ("Explore Local"), so I have to search for the patch queue folder again using Windows Explorer.
Feature request:
1. Please add "Edit Patch File" to patch context menu.
2. Please add "Explore Patch Queue" to patch context menu.
STR:
1. From your patch queue, try to view/edit the currently selected patch.
2. From your patch queue, try to explore the folder location of the patch queue.
Actual Result:
1. Have to search for the patch again using Windows Explorer (but thg knows the location)
2. Have to search for the patch folder again using Windows Explorer (but thg knows the location).
3. Unhappy user because it's not nice to search for things which are already right in front of you, and thg knows their location!
Expected Result:
1. Right-click on patch, then "Edit Patch File" from patch context menu to edit the patch file.
2. Right-click on patch, then "Explore Patch Queue" to explore the patch queue.
3. Happy user because thg is so efficient and helpful !!! :smiley:
Thank you very much for thg and all your efforts.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4919Pull specific bookmark also adds other older bookmarks2021-11-25T11:15:42ZBitbucket ImporterPull specific bookmark also adds other older bookmarks*Created originally on Bitbucket by [psuter (Peter Suter)](https://bitbucket.org/%7B48b289e8-68dd-4aa4-8d3a-6458c5363d69%7D/)*
1) I select a specific bookmark in "Synchronize"->"[x] Target: mybookmark".
2) Then I click "Pull".
Thi...*Created originally on Bitbucket by [psuter (Peter Suter)](https://bitbucket.org/%7B48b289e8-68dd-4aa4-8d3a-6458c5363d69%7D/)*
1) I select a specific bookmark in "Synchronize"->"[x] Target: mybookmark".
2) Then I click "Pull".
This also adds many old bookmarks (on ancestor changesets of the selected bookmark). Shouldn't it just pull that single selected bookmark instead?
Thankshttps://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/4918Incoming deselects target leading to unrestricted pull2020-06-21T11:09:08ZBitbucket ImporterIncoming deselects target leading to unrestricted pull*Created originally on Bitbucket by [psuter (Peter Suter)](https://bitbucket.org/%7B48b289e8-68dd-4aa4-8d3a-6458c5363d69%7D/)*
If I want to pull a bookmark:
1) I create that bookmark.
2) Then I can select that bookmark in "Synchro...*Created originally on Bitbucket by [psuter (Peter Suter)](https://bitbucket.org/%7B48b289e8-68dd-4aa4-8d3a-6458c5363d69%7D/)*
If I want to pull a bookmark:
1) I create that bookmark.
2) Then I can select that bookmark in "Synchronize"->"[x] Target: mybookmark".
3) Then I click "Incoming" to check what will be pulled.
4) Then I click "Pull".
But sometimes step 3) removes the bookmark from "[x] Target: mybookmark", so step 4) pulls everything instead of just the bookmark! This seems quite misleading / inconvenient / error prone.
(Maybe this happens only when the local bookmark is created on a changeset that is not an ancestor of the remote bookmark?)
Thanks