thg issueshttps://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues2020-06-21T09:59:28Zhttps://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/997unhandled IOError on visualdiff2020-06-21T09:59:28ZBitbucket Importerunhandled IOError on visualdiff*Created originally on Bitbucket by Anonymous*
~~~~
#!python
** Mercurial version (1.8.4). TortoiseHg version (2.0.5)
** Command: --nofork workbench
** CWD: C:\Users\Aurelian\Documents\Visual Studio 2010\Projects\sms360
** Extensi...*Created originally on Bitbucket by Anonymous*
~~~~
#!python
** Mercurial version (1.8.4). TortoiseHg version (2.0.5)
** Command: --nofork workbench
** CWD: C:\Users\Aurelian\Documents\Visual Studio 2010\Projects\sms360
** Extensions loaded: fixfrozenexts
** Python version: 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit (Intel)]
** Windows version: (6, 1, 7600, 2, '')
** Processor architecture: x86
** Qt-4.7.1 PyQt-4.8.3
Traceback (most recent call last):
File "tortoisehg\hgqt\filelistview.pyo", line 162, in vdifflocal
File "tortoisehg\hgqt\visdiff.pyo", line 216, in visualdiff
File "mercurial\copies.pyo", line 104, in copies
File "mercurial\context.pyo", line 692, in manifest
File "mercurial\util.pyo", line 169, in __get__
File "mercurial\context.pyo", line 622, in _manifest
File "mercurial\context.pyo", line 680, in status
File "mercurial\localrepo.pyo", line 1194, in status
File "mercurial\context.pyo", line 364, in cmp
File "mercurial\context.pyo", line 921, in data
File "mercurial\localrepo.pyo", line 652, in wread
File "mercurial\util.pyo", line 935, in __call__
File "mercurial\windows.pyo", line 20, in posixfile
IOError: [Errno 13] C:\NNNN\App_Data/DB.mdf: The process cannot access the file because it is being used by another process
~~~~https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/992Awkward behavior of the "default" group in repo registry2011-07-22T08:28:19ZBitbucket ImporterAwkward behavior of the "default" group in repo registry*Created originally on Bitbucket by [bozr](https://bitbucket.org/%7B86961d7e-9721-405e-9050-d49fe42662eb%7D/)*
The default group cannot be removed from the repo registry.
Is this because there should at least be one group available?
Th...*Created originally on Bitbucket by [bozr](https://bitbucket.org/%7B86961d7e-9721-405e-9050-d49fe42662eb%7D/)*
The default group cannot be removed from the repo registry.
Is this because there should at least be one group available?
The current behavior is quite awkward:
I have a bunch of repos each inside a group.
I also renamed the default group to something of my liking.
So, now it's not obvious which group is the former default group.
Apparently thg still remembers this, because sometimes I remove a repo group from the registry, however with the former default group the remove option is not available from the drop down menu.
IMHO it would be much nicer to prevent the user from deleting the last group if there is such a requirement.
I'm using TortoiseHg 2.1.1https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/990Opening a versionned directory2020-06-21T09:59:21ZBitbucket ImporterOpening a versionned directory*Created originally on Bitbucket by Anonymous*
{{{
#!python
** Mercurial version (1.8.3). TortoiseHg version (2.0.4)
** Command:
** CWD: C:\windows\system32
** Extensions loaded: fixfrozenexts
** Python version: 2.6.6 (r266:8429...*Created originally on Bitbucket by Anonymous*
{{{
#!python
** Mercurial version (1.8.3). TortoiseHg version (2.0.4)
** Command:
** CWD: C:\windows\system32
** Extensions loaded: fixfrozenexts
** Python version: 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit (Intel)]
** Windows version: (6, 1, 7601, 2, 'Service Pack 1')
** Processor architecture: x86
** Qt-4.7.1 PyQt-4.8.3
Traceback (most recent call last):
File "tortoisehg\hgqt\repowidget.pyo", line 616, in onRevisionSelected
File "tortoisehg\hgqt\revdetails.pyo", line 232, in onRevisionSelected
File "tortoisehg\hgqt\filelistmodel.pyo", line 82, in setContext
File "tortoisehg\hgqt\filelistmodel.pyo", line 159, in loadFiles
File "tortoisehg\hgqt\filelistmodel.pyo", line 117, in _buildDesc
File "mercurial\context.pyo", line 700, in files
File "mercurial\util.pyo", line 169, in __get__
File "mercurial\context.pyo", line 657, in _status
File "mercurial\localrepo.pyo", line 1182, in status
File "mercurial\context.pyo", line 364, in cmp
File "mercurial\context.pyo", line 921, in data
File "mercurial\localrepo.pyo", line 647, in wread
MemoryError
}}}https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/989.hgignore UI and files/patterns with #2020-06-21T09:59:20ZBitbucket Importer.hgignore UI and files/patterns with #*Created originally on Bitbucket by [kiilerix (Mads Kiilerich)](https://bitbucket.org/%7B557b6cb1-8bba-4f83-a28b-d729192b84ef%7D/)*
As requested by Steve in http://sourceforge.net/mailarchive/forum.php?thread_name=011101cc40d7%24eb6dce1...*Created originally on Bitbucket by [kiilerix (Mads Kiilerich)](https://bitbucket.org/%7B557b6cb1-8bba-4f83-a28b-d729192b84ef%7D/)*
As requested by Steve in http://sourceforge.net/mailarchive/forum.php?thread_name=011101cc40d7%24eb6dce10%24c2496a30%24%40jaquiery%40adinstruments.com&forum_name=tortoisehg-discuss :
mercurial/ignore.py has handling of # for comments and escaping of # for not being a comment anyway.
thg should apply the reverse transformation in the UI for ignoring files - probably just a
{{{
.replace('#', '\\#')
}}}https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/961"hg update" silently fails causing "mystery adds"2020-06-21T09:58:44ZBitbucket Importer"hg update" silently fails causing "mystery adds"*Created originally on Bitbucket by [ryanflegel (Ryan Flegel)](https://bitbucket.org/%7B4f32a8cc-c112-4b5d-b85a-081451ae9fc6%7D/)*
TortoiseHg Dialogs (version 2.1.1), Mercurial (version 1.9+10-e9264b45237d)
When a file is locked by a...*Created originally on Bitbucket by [ryanflegel (Ryan Flegel)](https://bitbucket.org/%7B4f32a8cc-c112-4b5d-b85a-081451ae9fc6%7D/)*
TortoiseHg Dialogs (version 2.1.1), Mercurial (version 1.9+10-e9264b45237d)
When a file is locked by another process and an Update is done to another revision where that file has been deleted, the file isn't physically removed from the hard drive, but the update still appears successful. This causes a problem when you merge in the other branch into your workspace--since the file is still physically there, it thinks you meant to keep it there as part of the merge process, so the file re-appears in the merge changeset, even though it was deleted in the other branch.
I assume the same problem exists if the file is modified.
In older version of TortoiseHg this update would have failed, so you couldn't accidentally re-add the file (although it did make a mess of your workarea).
Step-by-step to reproduce:
#Delete file in one branch (A)
#In a separate branch (B) with a common ancestor, lock a file with another process and update to Branch A.
#Merge Branch B into Branch A.
#As a result of the merge the file will remain, even though it was deleted in Branch B.
For those using Windows, here's a quick VBScript to lock a file:
{{{
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.OpenTextFile("filetolock.txt", 8, True)
WScript.Echo ("Press Enter to continue")
objFile.Close
}}}
Anyway, a warning or error would be preferred to this sneaky behaviour. We've had to delete the same files 3-4 times this week and it's only Wednesday :-)https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/952synchronized error on remote2020-06-21T09:58:31ZBitbucket Importersynchronized error on remote*Created originally on Bitbucket by Anonymous*
Hi all.
TortoiseHq 2.1.1(with Mercurial 1.9+10) --> remte synchronizing error
but,
TortoiseHq 2.1(with Mercurial 1.9) --> success
why???
no firewall*Created originally on Bitbucket by Anonymous*
Hi all.
TortoiseHq 2.1.1(with Mercurial 1.9+10) --> remte synchronizing error
but,
TortoiseHq 2.1(with Mercurial 1.9) --> success
why???
no firewallhttps://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/948QWidget: Must construct a QApplication before a QPaintDevice2020-06-21T09:58:28ZBitbucket ImporterQWidget: Must construct a QApplication before a QPaintDevice*Created originally on Bitbucket by Anonymous*
Using Mercurial-1.9, Python-2.7.0, PyQt-4.8.4, Qt-4.6.2
I get the following error when trying to execute 'thg'
QWidget: Must construct a QApplication before a QPaintDevice
Aborted
...*Created originally on Bitbucket by Anonymous*
Using Mercurial-1.9, Python-2.7.0, PyQt-4.8.4, Qt-4.6.2
I get the following error when trying to execute 'thg'
QWidget: Must construct a QApplication before a QPaintDevice
Aborted
This occurs both with a cloned repository and with the tortoisehg-2.1 tarball .
The platform is Redhat Enterprise Linux 5 on x86_64 . Python , Qt, PyQt are compiled from source with gcc 4.2.2https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/908Trying to import a bundle fails.2020-06-21T09:57:46ZassarbadTrying to import a bundle fails.The bundle was created by
$ hg --version
Mercurial Distributed SCM (version 1.6.4)
Here is the output. No idea how to get this to fixed-width font here ... the preview shows it all garbled :-|
~~~~
#!python
** Mercurial versi...The bundle was created by
$ hg --version
Mercurial Distributed SCM (version 1.6.4)
Here is the output. No idea how to get this to fixed-width font here ... the preview shows it all garbled :-|
~~~~
#!python
** Mercurial version (1.8.3). TortoiseHg version (2.0.4)
** Command: --nofork workbench --listfile C:\Users\Oliver\AppData\Local\Temp\THG8B07.tmp
** CWD: I:\hg
** Extensions loaded: fixfrozenexts, extdiff, keyword, mq, relink, transplant
** Python version: 2.6.6 (r266:84297, Aug 24 2010, 18:13:38) [MSC v.1500 64 bit (AMD64)]
** Windows version: (6, 1, 7601, 2, 'Service Pack 1')
** Processor architecture: x64
** Qt-4.7.1 PyQt-4.8.3
Traceback (most recent call last):
File "tortoisehg\hgqt\repowidget.pyo", line 282, in setBundle
File "tortoisehg\hgqt\thgrepo.pyo", line 42, in repository
File "mercurial\bundlerepo.pyo", line 188, in __init__
File "mercurial\changegroup.pyo", line 145, in read
File "mercurial\util.pyo", line 994, in read
File "mercurial\util.pyo", line 972, in splitbig
File "mercurial\changegroup.pyo", line 132, in generator
IOError: invalid data stream
~~~~
https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/862workbench: don't switch to commit tab by clicking qtip row2020-06-21T09:56:52ZBitbucket Importerworkbench: don't switch to commit tab by clicking qtip row*Created originally on Bitbucket by [Neutrino_Sunset (Neutrino Sunset)](https://bitbucket.org/%7Bbafd0fc9-2f29-449b-b68b-439e0ba30c28%7D/)*
Tested on: Win 7 Ultimate
Using: tortoisehg-2.1-hg-1.9-x64 (where can the full build number b...*Created originally on Bitbucket by [Neutrino_Sunset (Neutrino Sunset)](https://bitbucket.org/%7Bbafd0fc9-2f29-449b-b68b-439e0ba30c28%7D/)*
Tested on: Win 7 Ultimate
Using: tortoisehg-2.1-hg-1.9-x64 (where can the full build number be found?)
This is a difficult to explain issue so please forgive the step by step reproduction.
C:\Workspaces\HgTest>hg init HgTest
C:\Workspaces\HgTest>echo revision 1 > file1.txt
C:\Workspaces\HgTest>hg add
adding file1.txt
C:\Workspaces\HgTest>hg commit -m "r1"
C:\Workspaces\HgTest>echo revision 2 >> file1.txt
C:\Workspaces\HgTest>hg commit -m "r2"
C:\Workspaces\HgTest>echo revision 3 >> file1.txt
This gives to a new repository, a couple of commited changesets and some outstanding local modifications.
If at this point you right click HgTest in Windows Explorer and open the workbench everything is good.
In the Graph Log clicking any of the changeset entries displays the details of that changeset in Revision Details mode, and clicking on the Working Directory entry shows the outstanding modifications in Commit mode.
Now close the Workbench and do this. First a revert to clear local modifications.
C:\Workspaces\HgTest>hg revert -a
reverting file1.txt
Now create a patch and an outstanding modification.
C:\Workspaces\HgTest>hg qnew patch1 -m "patch1"
C:\Workspaces\HgTest>echo patch1 stuff >> file1.txt
Now open the Workbench again. At first glance everything looks good. On the toolbar the Revision Details button is pressed, in the Graph Log patch1 is highlighted and the changeset details and diff are displayed with nothing in them (which is correct since the patch has not been refreshed).
But now if you click any other revision or the Working Directory and then click back on patch1 instead of seeing the same Revision Details view again the UI instead switches into Commit mode as it normally does when you click the Working Directory.
This seems like a bug because you'd expect the UI to switch into the same mode when clicking the same item.
Now close the Workbench again and do this.
C:\Workspaces\HgTest>hg qrefresh
C:\Workspaces\HgTest>hg qnew patch2 -m "patch2"
C:\Workspaces\HgTest>echo patch2 >> file1.txt
C:\Workspaces\HgTest>hg qrefresh
C:\Workspaces\HgTest>echo more changes >> file1.txt
Now you have 2 patches, both refreshed and some outstanding local modifications. Open the Workbench again.
As before it opens looking good, patch2 is selected, the UI is in Revision Details mode and the correct diff of patch2 is displayed. But when you switch away from patch2 and then switch back to it, the UI no longer remains in Revision Details mode but instead switches to Commit mode.
In this state you can click on patch1 and see its contents, but if you click on patch2 instead of seeing its already refreshed contents in Revision Details mode (which you could see when the Workbench first opened) instead you now see a combination of its already refreshed changes mixed together with the outstanding changes.
This is inconsistent and confusing, and it leaves you with no way to see the already refreshed contents of the qtip patch.
I think that's a bug and that the correct behaviour is that selecting any changeset (repository or patch) should always present a Revision Details view, and that you should only ever see working copy modifications by clicking the Working Directory entry.
https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/851shellext: Pixelized icons in Properties dialog box2020-06-21T09:56:38ZBitbucket Importershellext: Pixelized icons in Properties dialog box*Created originally on Bitbucket by [dgolub (David Golub)](https://bitbucket.org/%7Bb3e0aa8d-934d-4707-a0ca-dedf92d90781%7D/)*
The TortoiseHg icon overlays appear pixelated in the standard Windows Properties dialog box. To reproduce th...*Created originally on Bitbucket by [dgolub (David Golub)](https://bitbucket.org/%7Bb3e0aa8d-934d-4707-a0ca-dedf92d90781%7D/)*
The TortoiseHg icon overlays appear pixelated in the standard Windows Properties dialog box. To reproduce this bug, navigate to any Mercurial repository in Windows Explorer, right click on a file under source code control, and select Properties from the context menu. The icon in the dialog box will appear pixelized.
*Attachments:* [properties](/uploads/8294809ba261acee88daf6bfd0ee9334/properties.png)[Windows-7-x64-ultimate](/uploads/c284d97e05adbc2d8d6a8523a921ccee/Windows-7-x64-ultimate.PNG)https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/810black on black (totally not visible) text with dark theme2022-06-22T07:39:18ZBitbucket Importerblack on black (totally not visible) text with dark theme*Created originally on Bitbucket by [tot-to](https://bitbucket.org/%7B72e8fc51-a3f8-45f1-b51b-e31316cdde8a%7D/)*
I am using dark theme, with totally black background and white text.
thg gets text color in diff section not from theme, b...*Created originally on Bitbucket by [tot-to](https://bitbucket.org/%7B72e8fc51-a3f8-45f1-b51b-e31316cdde8a%7D/)*
I am using dark theme, with totally black background and white text.
thg gets text color in diff section not from theme, but from the other location (hardcode?). I didn't find any option in thg, that can be change this behavior.
*Attachments:* [screen](/uploads/a0a2b4c98a89929c89934b81266e5702/screen.png)https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/801Pull before commit2020-06-21T09:55:32ZBitbucket ImporterPull before commit*Created originally on Bitbucket by [davidscherer (David Scherer)](https://bitbucket.org/%7B9a85f5d3-473a-40a2-b2a4-10751fad17f4%7D/)*
I often forget to pull from bitbucket before committing, and have to "undo" a commit when the push wa...*Created originally on Bitbucket by [davidscherer (David Scherer)](https://bitbucket.org/%7B9a85f5d3-473a-40a2-b2a4-10751fad17f4%7D/)*
I often forget to pull from bitbucket before committing, and have to "undo" a commit when the push warns about extra heads. I would love to have an option to "pull before commit", similar to "push after commit", which would automatically pull when I click commit. If the pull makes my working revision not a head (I don't have "update after pull" on), then I should see a warning and have a chance to cancel the commit.
I would also like to have a keyboard shortcut for "pull".https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/799Workbench: Check each repo for new incoming changelists2020-06-21T09:55:30ZBitbucket ImporterWorkbench: Check each repo for new incoming changelists*Created originally on Bitbucket by [alfonse (Jason McKesson)](https://bitbucket.org/%7B5709bf8f-1694-4941-a4e7-44d0ef50703f%7D/)*
The fact that the workbench has a registry of multiple repos is rarely taken advantage of in TortoiseHg. ...*Created originally on Bitbucket by [alfonse (Jason McKesson)](https://bitbucket.org/%7B5709bf8f-1694-4941-a4e7-44d0ef50703f%7D/)*
The fact that the workbench has a registry of multiple repos is rarely taken advantage of in TortoiseHg. This would be one way to do it: make it easy to test all of the repos in the registry have incoming changelists from their default destinations. You could also add the ability to test whether they have outgoing changelists.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/791No option to clone from an https repository with stored host fingerprint veri...2020-06-21T09:55:19ZBitbucket ImporterNo option to clone from an https repository with stored host fingerprint verification*Created originally on Bitbucket by Anonymous*
TortoiseHG provides the facilities to push/pull from an HTTP(S) repository using Verification with stored host fingerprint.
However this option is not available for the clone option. Ide...*Created originally on Bitbucket by Anonymous*
TortoiseHG provides the facilities to push/pull from an HTTP(S) repository using Verification with stored host fingerprint.
However this option is not available for the clone option. Ideally the same security dialog used for the Sync option is available in the Clone dialog to offer the same options.
The latest unstable release offers No Host validation option, but no option to perform Verification using stored host fingerprint.
https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/777MQ: Restore keyboard shortcuts for reordering patches2020-06-21T09:55:04ZBitbucket ImporterMQ: Restore keyboard shortcuts for reordering patches*Created originally on Bitbucket by [anpol (Andrei Polushin)](https://bitbucket.org/%7Bdcdaa227-6a43-473f-af9a-e87581f8b7b4%7D/)*
There are several places where patches could be reordered using drag-n-drop, but there are no keyboard sho...*Created originally on Bitbucket by [anpol (Andrei Polushin)](https://bitbucket.org/%7Bdcdaa227-6a43-473f-af9a-e87581f8b7b4%7D/)*
There are several places where patches could be reordered using drag-n-drop, but there are no keyboard shortcuts for reordering.
And the usability of current drag-n-drop is rather far from excellent (e.g. it doesn't indicate that the drop target is **between** items). As a result, the reordering is hardly usable.
For now, I document the keyboard shortcuts available in Thg 1.x series:
* Shift+Up - Extend selection Up
* Shift+Down - Extend selection Down
* Alt+Shift+Up - No action (Now: Extend selection Up)
* Alt+Shift+Down - No action (Now: Extend selection Down)
(I guess, all combinations with Alt key should be reserved for future use and prohibited for now).
* Ctrl+Up - Apply next patch (the head of the queue is at the bottom)
* Ctrl+Down - Unapply last patch (the head of the queue is at the bottom)
(In thg 1.x, the head of the queue is at the top of the window, so the reverse keys were used)
* Ctrl+Shift+Up - Reorder: Move the selected patches visually Up in the Queue
* Ctrl+Shift+Down - Reorder: Move the selected patches visually Down in the Queue
(Reordering is valid when the contiguous range of unapplied patches are selected)
I propose to add the shortcuts to the RepoWidget at least.
There is the "Reorder Patches" dialog that duplicates the behavior of the RepoWidget. The shortcuts could be applied there too, and I suggest to add the proper (toolbar) buttons for patch reordering.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/775Filelist icons (in RevDetails) should match the Changes column (of RepoWidget)2020-06-21T09:55:00ZBitbucket ImporterFilelist icons (in RevDetails) should match the Changes column (of RepoWidget)*Created originally on Bitbucket by [anpol (Andrei Polushin)](https://bitbucket.org/%7Bdcdaa227-6a43-473f-af9a-e87581f8b7b4%7D/)*
At this time there is now icon for the file in 'modified' state in filelist widget. At least there should ...*Created originally on Bitbucket by [anpol (Andrei Polushin)](https://bitbucket.org/%7Bdcdaa227-6a43-473f-af9a-e87581f8b7b4%7D/)*
At this time there is now icon for the file in 'modified' state in filelist widget. At least there should be one, so that all filenames are to have the same indentation.
In addition, I propose to match the colors displayed in the Changes column with the icon colors, like so:
* [Added] - Green color in the column and Green icon in the filelist widget.
* [Modified] - Orange color and icon, I propose the of pencil symbol.
* [Deleted] - Red color and icon, i.e. leave it as it now.
See the attached illustration.
*Attachments:* [thg-filelist-icons](/uploads/2aaf2375dca3a2c7d3e4cfed970282f9/thg-filelist-icons.png)https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/761"Hg Copy versioned item(s) here" in single folder does nothing2020-06-21T09:54:43ZBitbucket Importer"Hg Copy versioned item(s) here" in single folder does nothing*Created originally on Bitbucket by [DavidCary](https://bitbucket.org/%7B708ac6a6-b995-45d2-8ea6-ebaa7d5e67b6%7D/)*
I have a (long) source file I want to break into 2 smaller files.
I was told that the best way to do this (while main...*Created originally on Bitbucket by [DavidCary](https://bitbucket.org/%7B708ac6a6-b995-45d2-8ea6-ebaa7d5e67b6%7D/)*
I have a (long) source file I want to break into 2 smaller files.
I was told that the best way to do this (while maintaining full history)
involved the "Hg Copy versioned item(s) here" option. Is that right?
Alas, when I select that command, it does nothing.
**What I did**:
* Open up the working directory in the File Explorer, and confirm that the file has the green "committed" checkmark.
* Hover the mouse over the original file
* Hold down the right mouse button and drag into some whitespace inside the same folder, then let go of the button
* When the context menu pops up, choose "Hg Copy versioned item(s) here".
**What I expected** to happen:
I expected one or the other of these two options 1a or 1b:
* 1a. A dialog box pops up, asking me what new name I want to use.
* 1b. A dialog box never pops up. Instead, TortoiseHg instantly creates a new file named "Copy of (original_filename)", exactly the same name as if I had chosen the "Copy here" option rather than "Hg Copy versioned item(s) here" option.
In either case,
* 2. Eventually, the folder ends up with 1 more file than it had when I started. The new file should appear in the same folder as the original file, with a new name, but should otherwise be bit-for-bit identical to the original file.
**What actually happens**:
* a window briefly pops up and disappears, and the working folder is unchanged -- it has exactly the same number of files as when I started.
As far as I can tell, the "Hg Copy versioned item(s) here" command does nothing, and therefore is useless.
**Workaround 1**. Use TortoiseSVN.
With a different working directory that uses TortoiseSVN,
when I go through the same steps (selecting "SVN Copy versioned item(s) here",
I get a "Copy: New name for main.c" dialog box,
and after I type the new name I see it has created a new file with that name, as I expected.
Could some clever programmer somehow copy the TortoiseSVN code that implements this feature, and past it into TortoiseHg?
**Workaround 2**:
* Create a temporary directory in the same directory as the original file
* Hover the mouse over the original file
* Hold down the right mouse button and drag onto the temporary folder, then let go of the button
* When the context menu pops up, choose "Hg Copy versioned item(s) here".
* Open the temporary folder
* Choose "TortoseHg", then "Rename file..."
* When the dialog window pops up, delete the name of the temporary directory from the destination, and also give the file a name different than the original file.
* voila!
**details**:
I'm using the latest release: TortoiseHg version 2.0.4
with Mercurial-1.8.3, Python-2.6.6, PyQt-4.8.3, Qt-4.7.1,
on Windows XP Sevice Pack 3.
https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/729Enhance settings in order to set language in registry for explorer plug-in2020-06-21T09:54:05ZBitbucket ImporterEnhance settings in order to set language in registry for explorer plug-in*Created originally on Bitbucket by [tinne (Karsten Tinnefeld)](https://bitbucket.org/%7Be2d89e8b-c831-422c-922a-d5c9b2d84b44%7D/)*
When one sets the language in workbench settings, this has no effect on the explorer plug-in / context m...*Created originally on Bitbucket by [tinne (Karsten Tinnefeld)](https://bitbucket.org/%7Be2d89e8b-c831-422c-922a-d5c9b2d84b44%7D/)*
When one sets the language in workbench settings, this has no effect on the explorer plug-in / context menu extensions.
This is though counter-intuitive exhaustively documented in the FAQ, but I may not be the last to ask before reading, sorry :-(
Please consider adding the following functionality to workbench settings: Besides the language select box a button / link, "set locale for explorer plug-in" runs the windows registered application on ".reg" files in administrator mode.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/686Hide dot in first column when whitespace is visible2020-06-21T09:53:08ZBitbucket ImporterHide dot in first column when whitespace is visible*Created originally on Bitbucket by Anonymous*
In the commit window one can make whitespace visible. The first column is used to display the chars + or - for the diffs. But it shows dots in unchanged lines when whitespace is visible. Th...*Created originally on Bitbucket by Anonymous*
In the commit window one can make whitespace visible. The first column is used to display the chars + or - for the diffs. But it shows dots in unchanged lines when whitespace is visible. This can be confusing when I try to eliminate whitespace from otherwise empty lines. For those it displays “·LF” although there is no whitespace in that line. I suggest to keep the first column empty if no +, - or @ displayed.https://foss.heptapod.net/mercurial/tortoisehg/thg/-/issues/671Saving state of target in Synchronize tab2020-06-21T09:52:50ZBitbucket ImporterSaving state of target in Synchronize tab*Created originally on Bitbucket by [czarnyczarodziej (Piotr Klecha)](https://bitbucket.org/%7B0bfb38f6-a6af-4583-8336-9958c07dac8d%7D/)*
Currently the "Target:" checkbox and branch selection combo box in Synchronize tab are reset (chec...*Created originally on Bitbucket by [czarnyczarodziej (Piotr Klecha)](https://bitbucket.org/%7B0bfb38f6-a6af-4583-8336-9958c07dac8d%7D/)*
Currently the "Target:" checkbox and branch selection combo box in Synchronize tab are reset (checkbox unchecked, combo selects default branch) every time the repo/thg is closed. It would be better if the state was remembered or if thg allowed to set default state for each repo.