Brodie Rao <brodie@bitheap.org> [Fri, 02 Apr 2010 15:22:05 -0500] rev 10817
status: make use of output labeling
Brodie Rao <brodie@bitheap.org> [Fri, 02 Apr 2010 15:22:03 -0500] rev 10816
grep: make use of output labeling
Brodie Rao <brodie@bitheap.org> [Fri, 02 Apr 2010 15:22:00 -0500] rev 10815
ui: add ui.write() output labeling API
This adds output labeling support with the following methods:
- ui.write(..., label='topic.name topic2.name2 ...')
- ui.write_err(.., label=...)
- ui.popbuffer(labeled=False)
- ui.label(msg, label)
By adding an API to label output directly, the color extension can forgo
parsing command output and instead override the above methods to insert
ANSI color codes. GUI tools can also override the above methods and use
the labels to do GUI-specific styling.
popbuffer gains a labeled argument that, when set to True, returns its
buffered output with labels handled. In the case of the color extension,
this would return output with color codes embedded. For existing users
that use this method to capture and parse output, labels are discarded
and output returned as normal when labeled is False (the default).
Existing wrappers of ui.write() and ui.write_err() should make sure to
accept its new **opts argument.
Matt Mackall <mpm@selenic.com> [Thu, 01 Apr 2010 17:51:59 -0500] rev 10814
Merge with stable