TortoiseHg

--- you can reply above this line ---

Issue 251: Add 'export files in revision' feature
http://bitbucket.org/tortoisehg/stable/issue/251/add-export-files-in-revision-feature

Steve Borho / sborho on Mon, 24 May 2010 22:51:30 +0200:

Comment:
  implemented in the archive dialog of the Qt port

Changes:
  status: open -> resolved

-- 
This is an issue notification from bitbucket.org.
You are receiving this either because you are the
owner of the issue, or you are following the issue.

--- you can reply above this line ---

Issue 1245: Configure "hg serve" to run as a Windows service from TortoiseHg
http://bitbucket.org/tortoisehg/stable/issue/1245/configure-hg-serve-to-run-as-a-windows-service-from

Steve Borho / sborho on Mon, 24 May 2010 21:49:52 +0200:

Changes:
  status: new -> open

-- 
This is an issue notification from bitbucket.org.
You are receiving this either because you are the
owner of the issue, or you are following the issue.

--- you can reply above this line ---

New issue 1252: Add a link to ".rej" to the failure message when a MQ patch fails to apply
http://bitbucket.org/tortoisehg/stable/issue/1252/add-a-link-to-rej-to-the-failure-message-when-a-mq-patch-fails-to

amadawn on Mon, 24 May 2010 16:53:21 +0200:

Description:
  When a mercurial queue patch fails to apply TortoiseHg shows the error message that mercurial generates. If mq generated a "rejects" file the error message says so. For example:

applying 20.diff
patching file test.txt
Hunk #1 FAILED at 0
1 out of 1 hunks FAILED -- saving rejects to file test.txt.rej
patch failed, unable to continue (try -v)
patch failed, rejects left in working dir
errors during apply, please fix and refresh 20.diff
[command returned code 2 Mon May 24 12:03:02 2010]

It would be nice if "test.txt.rej" was a link that you could click to directly open the reject file, rather than having to open windows explorer and manually looking for the rejects file.

Cheers,

Amadawn


Responsible:
  tortoisehg
-- 
This is an issue notification from bitbucket.org.
You are receiving this either because you are the
owner of the issue, or you are following the issue.

--- you can reply above this line ---

New issue 1251: bug
http://bitbucket.org/tortoisehg/stable/issue/1251/bug

Anonymous on Mon, 24 May 2010 15:42:09 +0200:

Description:
  {{{
#!python
** Please report this bug to http://bitbucket.org/tortoisehg/stable/issues or tortoisehg-discuss@...
** Mercurial version (1.5.3).  TortoiseHg version (1.0.3)
** Command: --nofork log
** CWD: C:\AppServ\helpbank
** Extensions loaded: 
** sys.getwindowsversion(): (5, 1, 2600, 2, 'Service Pack 3')
** Processor architecture: x86
Recoverable runtime error (stderr):
Traceback (most recent call last):
  File "tortoisehg\hgtk\history.pyo", line 2710, in tree_button_press
  File "tortoisehg\hgtk\history.pyo", line 2723, in tree_popup_menu
  File "tortoisehg\hgtk\history.pyo", line 1192, in tree_context_menu
  File "mercurial\localrepo.pyo", line 130, in __getitem__
  File "mercurial\context.pyo", line 25, in __init__
  File "mercurial\revlog.pyo", line 516, in node
IndexError: list index out of range
Traceback (most recent call last):
  File "tortoisehg\hgtk\history.pyo", line 2710, in tree_button_press
  File "tortoisehg\hgtk\history.pyo", line 2723, in tree_popup_menu
  File "tortoisehg\hgtk\history.pyo", line 1192, in tree_context_menu
  File "mercurial\localrepo.pyo", line 130, in __getitem__
  File "mercurial\context.pyo", line 25, in __init__
  File "mercurial\revlog.pyo", line 516, in node
IndexError: list index out of range
Traceback (most recent call last):
  File "tortoisehg\hgtk\history.pyo", line 2710, in tree_button_press
  File "tortoisehg\hgtk\history.pyo", line 2723, in tree_popup_menu
  File "tortoisehg\hgtk\history.pyo", line 1192, in tree_context_menu
  File "mercurial\localrepo.pyo", line 130, in __getitem__
  File "mercurial\context.pyo", line 25, in __init__
  File "mercurial\revlog.pyo", line 516, in node
IndexError: list index out of range
Traceback (most recent call last):
  File "tortoisehg\hgtk\history.pyo", line 2710, in tree_button_press
  File "tortoisehg\hgtk\history.pyo", line 2723, in tree_popup_menu
  File "tortoisehg\hgtk\history.pyo", line 1192, in tree_context_menu
  File "mercurial\localrepo.pyo", line 130, in __getitem__
  File "mercurial\context.pyo", line 25, in __init__
  File "mercurial\revlog.pyo", line 516, in node
IndexError: list index out of range
Traceback (most recent call last):
  File "tortoisehg\hgtk\history.pyo", line 2710, in tree_button_press
  File "tortoisehg\hgtk\history.pyo", line 2723, in tree_popup_menu
  File "tortoisehg\hgtk\history.pyo", line 1192, in tree_context_menu
  File "mercurial\localrepo.pyo", line 130, in __getitem__
  File "mercurial\context.pyo", line 25, in __init__
  File "mercurial\revlog.pyo", line 516, in node
IndexError: list index out of range
Traceback (most recent call last):
  File "tortoisehg\hgtk\history.pyo", line 2710, in tree_button_press
  File "tortoisehg\hgtk\history.pyo", line 2723, in tree_popup_menu
  File "tortoisehg\hgtk\history.pyo", line 1192, in tree_context_menu
  File "mercurial\localrepo.pyo", line 130, in __getitem__
  File "mercurial\context.pyo", line 25, in __init__
  File "mercurial\revlog.pyo", line 516, in node
IndexError: list index out of range
Traceback (most recent call last):
  File "tortoisehg\hgtk\history.pyo", line 2710, in tree_button_press
  File "tortoisehg\hgtk\history.pyo", line 2723, in tree_popup_menu
  File "tortoisehg\hgtk\history.pyo", line 1192, in tree_context_menu
  File "mercurial\localrepo.pyo", line 130, in __getitem__
  File "mercurial\context.pyo", line 25, in __init__
  File "mercurial\revlog.pyo", line 516, in node
IndexError: list index out of range
Traceback (most recent call last):
  File "tortoisehg\hgtk\history.pyo", line 2710, in tree_button_press
  File "tortoisehg\hgtk\history.pyo", line 2723, in tree_popup_menu
  File "tortoisehg\hgtk\history.pyo", line 1192, in tree_context_menu
  File "mercurial\localrepo.pyo", line 130, in __getitem__
  File "mercurial\context.pyo", line 25, in __init__
  File "mercurial\revlog.pyo", line 516, in node
IndexError: list index out of range

}}}


-- 
This is an issue notification from bitbucket.org.
You are receiving this either because you are the
owner of the issue, or you are following the issue.

--- you can reply above this line ---

New issue 1250: Add settings panel to enable/disable installed extensions
http://bitbucket.org/tortoisehg/stable/issue/1250/add-settings-panel-to-enable-disable-installed

amadawn on Mon, 24 May 2010 15:09:19 +0200:

Description:
  It would be nice to be able to enable/disable extensions through a panel in the global settings tool.

Since some extensions require additional configuration, I think that a good start would be to create an "extension" panel on the global settings window. This extension panel could simply show a list of those extensions that are enabled, and let the user enable/disable those extensions that require no configuration (such as "Mercurial Queues").

For those extensions that require configuration perhaps a "template" config file could be created and that template could be used to create a configuration window that could be accessed through the extension panel. The extension configuration "template" could be quite simple. Perhaps a simple text file named as the extension (e.g. notify.ini) containing the list of keys that can be configured, an explanation of their meaning plus their default value and the list of valid values for each of them. For example, for the notify extension:

[notify]
sources=push
#%description=
#%type=choice
#%valid_values=serve|push|pull|bundle

config=
#%description=The filename of the configuration file
#%type=file

test=False
#%type:boolean

The idea is to put each key with its default values as you would put them in the mercurial.ini file. Then you could add extra information such as a description that could be shown when selecting the item in the extension configuration panel, a list of default values, the type of item (such as a choice for multi-selection items, or file to show a file browser, etc). Obviously any other similar syntax or method would be equally good as this is just an example of what could be done.

Using this sort of approach it would be quite simple to add support for any existing or new mercurial extension right into tortoisehg.

BTW I looked for an issue regarding this on the issue tracker but surprisingly I did not find any. I apologize if I missed it and is already on the pipeline (or if it has been discussed and rejected).

Cheers,

Amadawn

Responsible:
  tortoisehg
-- 
This is an issue notification from bitbucket.org.
You are receiving this either because you are the
owner of the issue, or you are following the issue.

--- you can reply above this line ---

Issue 993: Context menu icon is missing on Win XP
http://bitbucket.org/tortoisehg/stable/issue/993/context-menu-icon-is-missing-on-win-xp

Adrian Buehlmann / abuehl on Mon, 24 May 2010 10:08:29 +0200:

Comment:
  I'm not interested in spending my unpaid time trying to fix this myself, as we don't use Windows XP here anymore. Windows 7 is now standard here.

-- 
This is an issue notification from bitbucket.org.
You are receiving this either because you are the
owner of the issue, or you are following the issue.

--- you can reply above this line ---

Issue 1246: Use the TortoiseHg "mercury" icon for the TortoiseHg context menu
http://bitbucket.org/tortoisehg/stable/issue/1246/use-the-tortoisehg-mercury-icon-for-the-tortoisehg-context

amadawn on Mon, 24 May 2010 10:01:21 +0200:

Comment:
  Yes I am. It seems that this is a duplicate of issue #993 so you can mark it as such. Sorry!

Cheers,

Amadawn


-- 
This is an issue notification from bitbucket.org.
You are receiving this either because you are the
owner of the issue, or you are following the issue.

--- you can reply above this line ---

Issue 389: settings: represent configbool settings as tri-state toggles
http://bitbucket.org/tortoisehg/stable/issue/389/settings-represent-configbool-settings-as-tri-state

Steve Borho / sborho on Mon, 24 May 2010 05:35:57 +0200:

Changes:
  status: open -> wontfix

-- 
This is an issue notification from bitbucket.org.
You are receiving this either because you are the
owner of the issue, or you are following the issue.

--- you can reply above this line ---

Issue 716: Default Repository location setting
http://bitbucket.org/tortoisehg/stable/issue/716/default-repository-location-setting

Steve Borho / sborho on Mon, 24 May 2010 05:35:09 +0200:

Changes:
  component: settings -> clone

-- 
This is an issue notification from bitbucket.org.
You are receiving this either because you are the
owner of the issue, or you are following the issue.

--- you can reply above this line ---

Issue 1249: A failed unshelve leaves all hunks in the shelve file
http://bitbucket.org/tortoisehg/stable/issue/1249/a-failed-unshelve-leaves-all-hunks-in-the-shelve

Steve Borho / sborho on Mon, 24 May 2010 04:55:38 +0200:

Comment:
  Fixed by <<cset c5ca3c3e5b68>>

-- 
This is an issue notification from bitbucket.org.
You are receiving this either because you are the
owner of the issue, or you are following the issue.