From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <062201c178c5$e7460260$b6f7c6d4@cybercable.fr>
From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
References: <20011128185430.958E519A33@mail.cse.psu.edu> <200111281909.fASJ9xT58241@devil.lucid> <20011129074900.F317@cackle.proxima.alt.za> <054201c1789f$5538bf00$b6f7c6d4@cybercable.fr> <20011129125035.H317@cackle.proxima.alt.za>
Subject: Re: [9fans] Python filesystem
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Date: Thu, 29 Nov 2001 12:06:32 +0100
Topicbox-Message-UUID: 2c8bf930-eaca-11e9-9e20-41e7f4b1d025

> MH struck me as clumsy more because of the selection of module
> functions and names than out of a failing in the concept.  After all,
> it is the nature of Unix to have simple commands that can be strung
> together to produce complex results, where does MH's concept fail?

MH is too interactive.

Without trickery you can't really build meta-tools with it.

You know, the power of the shell/rc and the pipeline etc...

IIRC you couldn't use B as your $EDITOR with MH comp.

With my cut down, simpler version:

    EDITOR=B
    com
    <edit with sam>
    del

With sam you could have multiple messages being edited at once
and you del[iver] them as needed.