Hey there, I'm running Windows 7 64-bit and am using Sublime Text 2 Beta, Build: 2165. I installed SublimeHg via the Package Control package and after discovering the CLI that SublimeHg provides, made the Sublime Text 2 executable my default editor for Mercurial commit-messages.
editor = "C:\Program Files\Sublime Text 2\sublime_text.exe"
The problem is the following:
> hg commit
abort: empty commit message
This happens instantly after having typed "commit" and although a new tab opens that would potentially allow me to enter the commit message, it's useless at that point -- this only leaves me with directly passing the actual message via the "-m" command-line parameter.
Am I forgetting something? And if I am not: Could SublimeText 2 possibly implement a command-line parameter that would keep the "command-line channel", for a lack of a better term, open until the tab, in which the file is opened, is closed?