Benjamin Rutt [EMAIL PROTECTED] writes:
I have been using the bbdb for about two months now and I feel like I
am using it wrong. I spend all my time tweaking the
bbdb-ignore-some-messages-alist for email addresses I don't want
noticed, to protect them from being automatically added (I have
Nix [EMAIL PROTECTED] writes:
the notice hook gets called a
lot --- e.g., when updating records, as well as when looking at them,
No, it doesn't. Oops. (It even explicitly mentions that case in the
docstring.)
--
`Normally, we don't do people's
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
I have been using the bbdb for about two months now and I feel like
I am using it wrong. I spend all my time tweaking the
bbdb-ignore-some-messages-alist for email addresses I don't want
noticed, to protect them from being automatically added (I have
that turned on for gnus mail groups).
I don't disagree. It was just that given the original poster's
complaint, it appeared to me that he was looking at bbdb as more of an
address book.
--
Dave Goldberg
[EMAIL PROTECTED]
___
bbdb-info mailing list
[EMAIL PROTECTED]
I took a totally different approach; I decided that I wanted someone in my
bbdb if I replied to their email. So, as a gnus user, I did this:
(defun pdf-bbdb/gnus-force-create ()
"Add bbdb entry for this message."
(interactive)
(let ((bbdb/news-auto-create-p t))
Alex Schroeder [EMAIL PROTECTED] writes:
The issue is still undecided. A long time ago I wrote up a patch that
transformed all zip codes into strings and did away with all the
datastructure cruft that is used to validate zip codes. Since the zip
codes were saved as plain text strings, my
