I don't know if your emailing me directly was intentional or not, but I
think this discussion belongs on the list.

Jon Steinhart <[EMAIL PROTECTED]> writes:
> > Jon Steinhart <[EMAIL PROTECTED]> writes:
> > >      edit            re-edit using the same editor that was used on the
> > >                      preceding round unless a profile entry
> > >                      "<lasteditor>-next: <editor>" names an alternate editor
> > >      edit <editor>   invoke <editor> for further editing
> > >      refile +folder  refile the draft into the given folder
> > >      mime            process the draft as MIME composition file using
> > >                      the "buildmimeproc" command (mhbuild by default)
> > >      display         list the message being distributed/replied-to
> > >                      on the terminal
> > >      list            list the draft on the terminal
> > >      send            send the message
> > >      send -watch     send the message and monitor the delivery process
> > >      push            send the message in the background
> > >      whom            list the addresses that the message will go to
> > >      whom -check     list the addresses and verify that they are
> > >                      acceptable to the transport service
> > >      quit            preserve the draft and exit
> > >      quit -delete    delete the draft and exit
> > >      delete          delete the draft and exit
> > >      cd [dir]        change directory from which attachments are read
> > >      pwd             print director from which attachments are read
> > >      ls [ls-options] list files in attachment directory
> > >      attach files    attach files to draft
> > 
> > I would put 'attach' just before 'mime' since they're related, and that
> > would be the usual invocation order.
> 
>       Thanks for the feedback.  I was trying to keep the four new commands
>       together for no particular reason.  

Oh, I didn't even notice the other three new commands.  This is the reason I
suggested posting your changes in diff format (I know you couldn't do that
with the mhattach man page).  Well, it's probably best for them to all go
together (mime and your 4 new commands).

Now that I'm looking at them, I see that you need to change "director" to
"directory" on the "pwd" line.

>       I couldn't discern any order to the list.

Yes, that always bothers me when random order is used to list options and
such.  Often in such cases I alphabetize the existing items, as alphabetic
order is certainly better than no order at all, and makes it easier to find
things.

> > Also, presumably the command is not "attach files" and "files" should be
> > "<files>", right?
> 
>       Yes.  Was not clear to me that <> should be used.

Well, that's standard convention in ASCII for distinguishing between literal
commands and variable arguments.

> > >      Mhattach does not  actually  add  attachments  to  a  draft.
> > >      Instead,  it appends a directive in mhbuild(1) MIME composi-
> > >      tion  file  format  to  the  draft  for   each   attachment.
> > >      Mhbuild(1) must be invoked prior to sending in order to con-
> > >      vert the composition file into a MIME message  with  attach-
> > >      ments.  This is typically done in whatnow(1).
> > 
> > I think you should make it clear somewhere in here that mhattach is a
> > friendlier wrapper around the mhbuild directives, and that in the past they
> > had to be added manually (and still can, if desired).
> 
>       OK.  Yeah, I thought about having a way to delete attachments but
>       it was far easier to do that in the editor.

Ah yes.  You probably ought to explicitly mention that too (that directives
must be deleted manually), in the same area.

-----------------------------------------------------------------------
Dan Harkless                   | To prevent SPAM contamination, please 
[EMAIL PROTECTED]      | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW.  Thank you.     

Reply via email to