bug#10406: 24.0.92; mail-extract-address-components returns strange results

bug#10406: 24.0.92; mail-extract-address-components returns strange results

[Sam Steingold]

In GNU Emacs 24.0.92.5 (x86_64-unknown-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2011-12-28 on t520sds
Windowing system distributor `The X.Org Foundation', version 11.0.11004000
configured using `configure  '--with-wide-int''

I find this result surprising (emacs -Q):
  (mail-extract-address-components "foo.bar@quux.com <foo.bar@quux.com>")
==>  ("foo" "foo.bar@quux.com")
I expected either
  (nil "foo.bar@quux.com")
or
  ("foo bar" "foo.bar@quux.com")


-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11004000
http://jihadwatch.org http://truepeace.org http://camera.org
http://memri.org http://palestinefacts.org http://dhimmi.com http://ffii.org
nobody's life, liberty or property are safe while the legislature is in session

bug#10406: 24.0.92; mail-extract-address-components returns strange results

[Lars Ingebrigtsen]

Sam Steingold <sds@gnu.org> writes:

> I find this result surprising (emacs -Q):
>   (mail-extract-address-components "foo.bar@quux.com <foo.bar@quux.com>")
> ==>  ("foo" "foo.bar@quux.com")
> I expected either
>   (nil "foo.bar@quux.com")
> or
>   ("foo bar" "foo.bar@quux.com")

Yes, that function is weird.  I've updated the doc string to it to refer
users to `mail-header-parse-address' instead.

(mail-header-parse-address "foo.bar@quux.com <foo.bar@quux.com>")
=> ("foo.bar@quux.com" . "foo.bar@quux.com")

Packages that then want to display the "name" "foo.bar@quux.com" can
then do whatever they want with it...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no