Timothy Brownawell wrote:
Input for monotone automate stdio now has the format
'l'length':'arg[length':'arg...]'e'
, as there were problems mentioned with the previous format. Characters
between the 'e' for one command and the 'l' for the next are ignored
(except for 'l', of course).
Output now
On 5/20/05, Nathaniel Smith [EMAIL PROTECTED] wrote:
On Fri, May 20, 2005 at 10:36:32AM -0500, Timothy Brownawell wrote:
How about a series of length colon string items, like we were
thinking for the output?
7:parents40:0123456789abcdef0123456789abcdef01234567
Hmm, re-read my original
On Fri, May 20, 2005 at 10:36:32AM -0500, Timothy Brownawell wrote:
On 5/19/05, Nathaniel Smith [EMAIL PROTECTED] wrote:
On Wed, May 18, 2005 at 07:13:11PM -0500, Timothy Brownawell wrote:
It uses operator(istream, string) . So items are whitespace
separated, and whitespace is ignored.
Well, I'd see if everyone else is happy first, but personally that looks good
to me.
Whats the difference between 200 and 290?
I also think that the first line should echo back the command with its
arguments.
This would mean something like:
400 ERROR uknown /etc/foo
401 ERR errno code FILE NOT
On 5/17/05, Joel Crisp [EMAIL PROTECTED] wrote:
Yep, a number at the beginning of each line. It lets you detect the start of
the next header, distinguish different types of output
easily, handle optional or repeated blocks of output etc. It also allows you
to detect badly or prematurely
There've been some requests for a way to run multiple automate commands
without needing a new monotone process for each. There's now a new
command, monotone automate stdio that takes automate commands on
stdin. Currently, it prefixes the output of each command with the line
###BEGIN command### and
