Article View: gnu.emacs.bug
Article #99246(none)
From: nixpbe!uucp
Date: Tue, 16 Oct 1990 21:54
Date: Tue, 16 Oct 1990 21:54
60 lines
2931 bytes
2931 bytes
>From uucp Wed Oct 17 05:37 WST 1990 remote from nixsin To: nixpbe!unido!gnu-emacs-bug Path: nixsin!nixpbe!nixbur!linus!agate!ucbvax!tut.cis.ohio-state.edu!mumps.plus5.com!hokey From: hokey@mumps.plus5.com Newsgroups: gnu.emacs.bug Subject: Re: mh-e questions Message-ID: <22992.654970164@mumps> Date: 3 Oct 90 15:09:24 GMT References: <9010031454.AA02102@wucs1.wustl.edu> Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 45 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
Technical Details
Message-ID:
<9010162154.AW25791@unido.informatik.uni-dortmund.de>Path:
arc1-ca.pugleaf.net!gmdzi!unido!isaak!escher!nadia!smurf!ira.uka.de!sol.ctr.columbia.edu!cica!tut.cis.ohio-state.edu!relay.eu.net!nixpbe!uucpShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fb2f1,f1dbc4b61e8e8143 X-Google-Attributes: gidfb2f1,public X-Google-ArrivalTime: 1990-10-16 14:54:21 PST Path: arc1-ca.pugleaf.net!gmdzi!unido!isaak!escher!nadia!smurf!ira.uka.de!sol.ctr.columbia.edu!cica!tut.cis.ohio-state.edu!relay.eu.net!nixpbe!uucp From: nixpbe!uucp@relay.eu.net Newsgroups: gnu.emacs.bug Subject: (none) Message-ID: <9010162154.AW25791@unido.informatik.uni-dortmund.de> Date: 16 Oct 90 21:54:21 GMT Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 60 Approved: bug-gnu-emacs@prep.ai.mit.edu Posted: Tue Oct 16 22:54:21 1990