Mats Lidell wrote (of bbdb-obsolete-net.el):

> [...] nearly what I wanted. There are more attributes then net. When
> testing the code I realized that it wouldn't stop the notice-hook to
> do it's work. So visiting an old email will, depending on the
> definition of the bbdb-auto-notes-alist, possibly do some unwanted
> things.
> 
> So when there is an obsolete-net found auto-notes'ing should be
> disabled so that not old values are inserted in other fields.

This is very similar to a long-standing wish of mine which I've never
articulated here - what I'd like is for the BBDB to become effectively
read-only for certain mailboxes (or groups, in gnus).  Then I could
see the BBDB records, where these exist, when trawling through old
mailboxes but without any interaction or accidental pollution.  

I had a go at doing this ages ago by toggling the global
bbdb-readonly-p flag in an auto-create-hook but it didn't seem to work
very well (presumably not all the places in the code which would need
to check bbdb-readonly-p if it was changing regularly actually do so)
and is obviously not the Right Way to get the behaviour I want.

Any ideas?  Maybe I should try doing something in the bbdb-notice-hook
instead...

RobF said 

> I use a hook to ignore all but my inboxes for annotation

Can we see it?

Thanks,

Patrick



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/

Reply via email to