Fwd: Re: How hg signals error and aux messages

[Jan Vrany]

Yes, I've read this, but unfortunately I haven't found answers
to following questions:

- Is an error alwyas indicated by a line to stderr (or error channel)
starting with 'abort: '?
- Is an error always indicated on stderr (or error channel) before
command output?
- Where are auxiliary messages such as 'invalidating branch cache (tip
differs') written?

Also, I haven't found command's output "grammar" - how the output
(stdout or 'o'utput channel) of an hg merge command (for instance)
look like.

Actually, I do have a feeling and my brief experiments shows,
that command server solves only the problem of startup (and
maybe language neutrality) and does not specify the output of
individual HG commands like merge,  push, update. Am I wrong?

Jan



On 29/01/13 13:31, Mads Kiilerich wrote:
> On 01/29/2013 01:56 PM, Jan Vrany wrote:
>> Hi guys,
>>
>> I'm working on an Mercurial abstraction layer for Smalltalk.
>
> The main answer to your questions is
> http://mercurial.selenic.com/wiki/CommandServer
>
> /Mads