Shelve with the '#' simbol in the name

Issue #765 resolved
Eugene Olenev
created an issue



Mercurial version (1.8.3). TortoiseHg version (2.0.4) Command: --nofork workbench CWD: D:\Projects\AllScriptsHG\UECPortal Extensions loaded: fixfrozenexts, extdiff, mq, purge, convert 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\workbench.pyo", line 528, in forwarder File "tortoisehg\hgqt\repowidget.pyo", line 497, in shelve File "tortoisehg\hgqt\shelve.pyo", line 189, in init File "tortoisehg\hgqt\shelve.pyo", line 412, in refreshCombos File "tortoisehg\hgqt\shelve.pyo", line 439, in comboBChanged File "tortoisehg\hgqt\thgrepo.pyo", line 249, in changectx File "mercurial\localrepo.pyo", line 576, in changectx File "mercurial\localrepo.pyo", line 206, in getitem File "mercurial\context.pyo", line 27, in init File "mercurial\localrepo.pyo", line 551, in lookup RepoLookupError: unknown revision 'D:\Projects\AllScriptsHG\UECPortal.hg\shelves#31888. PayerPath. Add'


Comments (12)

  1. Steve Borho

    I'm unable to reproduce this problem. I can create a shelf file with # and use it just fine.

    However, I'm unable to convince Windows to allow me to create a file with << or >> in the name

    The fixes for #832 may have resolved this

  2. Anonymous

    I created a shelve with ":" in the name and now im not able to reopen the shelve.

    It Created the file and stop the naming befire the ":". Ex : I created "Dev : for me "

    If i go in "C:\Inetpub\wwwroot\.hg\shelves" i see the Shelve named "Dev " and the file is not accesible by windows i cant rename or delete the file.

    What can i do?

  3. Daniel Dagenais

    Ok for the moment i renamed the folder shelves2 and copy my correcte shelve in a new folder named shelves and it solve the problème for now.

    But i think you should add a warning pop up to not use ':' in the Shelve Name.


  4. Log in to comment