[RFC] New feature: --batch to accept command sequences from stdin (or file)

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jari Aalto+mail.perl wrote:
> Originally I was more thinking the language interpreter startup time,
> which I expected to be the problem. In PII 400Mhz/512M/W2k/Cygwin this
> command
> 
>    $ time python -c "exit;"
> 
> takes average of 1.5 sec (real). To run 3 commands in series, it would
> take total:

That is scary.  My box here is 115x as fast as that: 0.13s

We have been specifically targetting modern or nearly-modern machines
with bzr, (1.5 GHz has been the figure in my mind) but I don't think
we're opposed to fixes that help slower systems.

> hence my question if --batch could be considered.

Is that going to be enough?  I would think normal bzr operations commit
and revert would be way too slow.

>>>It would be nice if bzr somehow accepted commands to run from 
>>>stdin, from file or command line. Something like:
>>
>>There is already the "bzr serve" plugin.  See also the "bzr shell"
>>command in bzrtools, for interactive use.
> 
> 
> OK, Where can I learn more about the "serve" plugin?

Sorry, it's "service".  You can find it on the PluginRegistry:

http://bazaar-vcs.org/PluginRegistry

> Could the "serve" plugin be included in the Core? This sounds like it
> would help people using Cygwin version of python.

Given that it uses C, probably not.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEmcaf0F+nu1YWqI0RAqmvAJ9gFja7efVNyse2FHi70MiX30jXJACdFxg2
laS5KHRnf2KCXJYJhjEzHEA=
=lszP
-----END PGP SIGNATURE-----