The docstring for `bbdb-notice-hook' states
,----
| Also note that bbdb-change-hook will NOT be called as a result of any
| modifications you may make to the record inside this hook.
`----
As far as I can see, this is incorrect. It *should* be correct, because
it is very annoying to have the change-hook called just because the
notice-hook is recording things in there --- but this does not appear to
be implemented; bbdb-change-hook is called whenever a change happens,
even if we are underneath the bbdb-notice-hook.
I am working around this in the BBDB expiry code, but I think this
should probably be fixed. (If others agree I can spin a patch to fix
it.)
If it *is* fixed, I think the bbdb-after-change-hook should also be
suppressed. (Also, should the bbdb-notice-hook suppress *any* firing of
the bbdb-change-hook inside itself, or only that for records for which
it is being fired? The latter is arguably more correct, but harder to
implement.)
--
`Normally, we don't do people's homework around here, but Venice
is a very beautiful city, so I'll make a small exception.'
--- Robert Redelmeier compromises his principles
_______________________________________________
bbdb-info mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/bbdb-info
