Intermediate review for SF #1708292

This patch causes mh-edit-again to read the components file and insure
that all headers specified in the components file are present in the new
draft.

It makes use of mh-modify-header-field, so if a value is specified for a
header in the components file, that value will be added to the header in
the draft, unless it is already present.

The one thing I need to do is add support for scanning address fields
for aliases and expanding them.  Otherwise, if an alias was specified on
a cc: field and it was expanded on the draft, it would be appended to
the cc: field in the draft.

At this point I'm looking for feedback on my design.  Including answers
to these questions:

1) Should any of mh-extract-header, mh-components-to-list,
   mh-find-components be moved to mh-utils.el or another file.

2) Is there a more correct function to use than add-to-list in
   mh-compoenents-to-list?  Add-to-list insures entries are unique and
   I'm not sure we need to do that.

Thanks!

Jeff

-- 
Jeffrey C. Honig <jch <at> honig.net>
http://www.honig.net/jch
GnuPG ID:14E29E13 <http://www.honig.net/jch/key.shtml>

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox

_______________________________________________
mh-e-devel mailing list
mh-e-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mh-e-devel