🚀 go-pugleaf

Thanks for the response!  I'll check out the new version.

On an aside, I patched my copy from 18.55 because I wanted "delete" to
refile messages in a folder, and due to a variety of subtle problems, it
has to be done via a script instead of via the .mh_profile.  The man
page for rmm hints at this, and I recall seeing the explanation
somewhere in one of the docs.

Perhaps I'm missing something, but I got the impression that when
composing or replying to messages via mh-e, the header section was built
up via mechanisms built in to mh-e, and not going through a *comps file.

If I invoke a "make some mail and send it" from mh-e (be it a forward,
reply, compose, redist, whatever), I'd like to pass the headers through
a filter which would generate Fcc: lines for me.  As it is possible to
add headers while composing messsages, I'd like to be able to call that
function interactively.

For example, I `a'nswered this message and got these headers:

  To: Stephen Gildea <alexander.bbn.com!gildea>
  cc: prep.ai.mit.edu!bug-gnu-emacs, cs.wisc.edu!larus

I'd like to have had the following lines in there as well:

  Fcc: +alexander.bbn.com/gildea
  Fcc: +prep.ai.mit.edu/bug-gnu-emacs
  Fcc: +cs.wisc.edu/larus

I'll play some more with my replcomps file to see if it helps; if it
does, that's part of the battle.  I'd like to have a function which I
could call interactively to do the same thing.  I'd like to be familiar
enough with elisp that I could send it tou you, instead of asking for
it, too!

I also just noticed that the From: line in your message to me was:

  From: Stephen Gildea <gildea@alexander.bbn.com>

but mh-e translated that into bang format.

I'll get the current version of mh-e.el and dive in to all this a bit
deeper.

Hokey