From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: ietf-drums-parse-address, gnus-extract-address-components, mail-extract-address-components
Date: Tue, 17 Oct 2006 15:58:28 +0100 [thread overview]
Message-ID: <g69fydnq99n.fsf@lifelogs.com> (raw)
In-Reply-To: <v98xjgvsxr.fsf_-_@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon\, 16 Oct 2006 23\:42\:24 +0200")
On 16 Oct 2006, reinersteib+from-uce@imap.cc wrote:
> We have `gnus-extract-address-components' (which uses the variable
> `gnus-extract-address-components'), `mail-extract-address-components' and
> `ietf-drums-parse-address':
...
> I don't know what's the difference between
> `mail-extract-address-components' and `ietf-drums-parse-address'
> (speed, reliability, ...)? Anyone?
I looked at ietf-drums-parse-address and it looked right. But as you
note, there are three ways to do the same thing. So I would unify
everything under gnus-extract-address-components with an optional
'mail or 'ietf parameter or something like that (user should be able
to override it, I think). Otherwise we'll just run into the same
problem next year.
> It looks like the "@" in the `FULL-NAME' confused
> `gnus-extract-address-components'. Maybe we can also add a simple fix
> in `gnus-extract-address-components' for this quite common case.
That's fine, but it's still quick-and-dirty and for spam-check-BBDB
for instance it's OK to be a little slower; getting bad results is
much worse.
Let me know. I honestly don't have a preference as long as the bug is
fixed and everyone is happy.
Ted
next prev parent reply other threads:[~2006-10-17 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87mz851t59.fsf@mobile.repose.cx>
[not found] ` <g69hcy4t8g0.fsf@lifelogs.com>
2006-10-16 21:42 ` ietf-drums-parse-address, gnus-extract-address-components, mail-extract-address-components (was: bug in spam-check-BBDB) Reiner Steib
2006-10-16 22:47 ` ietf-drums-parse-address, gnus-extract-address-components, mail-extract-address-components Katsumi Yamaoka
2006-10-16 23:06 ` Miles Bader
2006-10-16 23:58 ` Katsumi Yamaoka
2006-10-17 14:58 ` Ted Zlatanov [this message]
2006-10-28 10:22 ` Reiner Steib
2006-10-30 3:23 ` Katsumi Yamaoka
2006-10-30 11:56 ` Reiner Steib
2006-10-30 19:00 ` Ted Zlatanov
2006-11-14 17:21 ` Reiner Steib
2006-11-14 23:41 ` Katsumi Yamaoka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=g69fydnq99n.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).