newby question: styling the hg status command

[Matt Mackall]

On Tue, 2008-05-06 at 18:51 +0200, Paul R wrote:
> Matt Mackall <mpm at selenic.com> writes:
> 
> > On Tue, 2008-05-06 at 08:11 -0500, Lance Perry wrote:
> >> Can the 'hg status' command be styled like the 'hg log' command?
> >
> > Nope, sorry.
> 
> I sent an email on 29 of April about the need of mercurial to express
> its state and history in an easy-to-parse way. I proposed xml because
> it looks natural in this case. The syntax must be defined once for
> good and not be broken by later updates, even if internals change a
> bit.

The output of status is already defined once and for good and it's a
hell of a lot easier to parse than XML.

> This is REQUIRED to integrate Mercurial with all those popular bug
> tracking tools.

Required? Hardly. Handy I'll grant. Our template language currently has
exactly one deficit that prevents making a proper XML log output: we
don't have a way to put a final end-of-changesets close tag on. That
appears to be as easy as adding a destructor or done() method to the
changeset_templater (and changeset_printer) classes in cmdutil.py.

-- 
Mathematics is the supreme nostalgia of our time.