[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] automate stdio, really
From: |
Thomas Moschny |
Subject: |
Re: [Monotone-devel] automate stdio, really |
Date: |
Wed, 30 Aug 2006 15:05:02 +0200 |
User-agent: |
KMail/1.9.4 |
On Wednesday 30 August 2006 14:25, Richard Levitte - VMS Whacker wrote:
> Isn't this going a bit far? Soon, we will have automate commands for
> all "normal" commands if we continue like this. Isn't that getting a
> bit ridiculous, not to mention the risks involved, like having to
> update the same command in two places all the time?
>
> I dunno what the solution is. Maybe have stdio work with non-automate
> commands as well, and having all commands be able to output stdio-
> specific data that would be more oriented for scripts, as well as
> human readable output, all depending on how the command was called.
Ok, this is a taboo subject, but it imho raises the mtn-library and
mtn-frontend(s) discussion again.
Of course we will end up with all commands available in automate. If a command
wasn't useful, it would not be in the 'normal' cmdline interface either.
--
Thomas Moschny <address@hidden>
pgpoVgM14eufO.pgp
Description: PGP signature
- [Monotone-devel] automate stdio, really, Richard Levitte - VMS Whacker, 2006/08/30
- Re: [Monotone-devel] automate stdio, really, Jon Bright, 2006/08/30
- Re: [Monotone-devel] automate stdio, really, Timothy Brownawell, 2006/08/30
- Re: [Monotone-devel] automate stdio, really,
Thomas Moschny <=
- Re: [Monotone-devel] automate stdio, really, Nathaniel Smith, 2006/08/30