>>>>> Barry A Warsaw writes:
>>>>> "msj" == Martin Sjolin <[EMAIL PROTECTED]> writes:
BAW> [Remember I don't use BBDB and know next to nothing about it. -BAW]
That is OK with me ;-)
BAW> Would it be useful if sc-mail-process-headers ran a hook as the last
BAW> thing it did? Something like:
BAW> (defun sc-mail-process-headers (start end)
BAW> [ ... ]
BAW> (run-hooks 'sc-mail-process-headers-hook))
looks great!
BAW> At this point all the mail info should be in sc-mail-info. You would
BAW> also probably need an API to add arbitrary fields and values to
BAW> sc-mail-info (since you probably don't want to be hacking that list
BAW> manually).
yes, this would be perfect, with a "defined" interface to sc-mail-info
for adding/modify pairs to it. Second, what is the "best" cleanest
way (with the future in mind) to retrieve an attribution from
BBDB - using the bbbd-attribution (as i reposted Tom's code) or
using sc-consult (which is not "good" enough: e.g.
(setq sc-attrib-selection-list
'(("From" ((".*" . (bbdb/supercite-get-attr-new
(sc-mail-field "from")))))))
1. "From" is constant ...
2. ".*" should really only match against the e-name addresses
in BBDB, that is, allowing a predicate functions instead of ".*"
3. Allowing a functional expression instead of (infokey ((regexp . ))) ?
thought? BTW, i have had one report of people having problems
when using the code for retreiving name from BBDB, but i have
not had the time to track it down (yet).
later,
msj
--
Martin Sj\"olin | http://www.ida.liu.se/labs/iislab/people/marsj
Department of Computer Science, LiTH, S-581 83 Link\"oping, SWEDEN
phone : +46 13 28 24 10 | fax : +46 13 28 26 66 | e-mail: [EMAIL PROTECTED]
