Here is what appears to be abetter fix. This uses
(set-text-properties start end nil) to turn off all text properties in the
buffer that mail-extract-address-components uses.
~/emacs-19.29/lisp> diff -c mail-extr.el~ mail-extr.el
*** mail-extr.el~ Mon May 29 03:06:56 1995
--- mail-extr.e
> "Martin" == Martin Maechler <[EMAIL PROTECTED]> writes:
Martin> I've started using font-lock yesterday; and now bbdb starts
Martin> behaving funnily, when mail reading, it asks (for every
Martin> entry!)
Martin> replace "Martin B. Maechler" by "Martin B. Maechler" ?
The problem i
> "Jack" == Jack Vinson <[EMAIL PROTECTED]> writes:
Jack> That patch I sent only works if font-lock is a current feature.
Jack> I just realized this on starting a new emacs. There must be a
Jack> better way to clear a buffer/region of all non-default face
Jack> information.
It turns out that, in many cases, it is quite annoying that
mail-fetch-field (and a few pieces of mail-extr, too) deliver the mail
fields with the contained (visual) properties.
Should they do that ? Or should the properties have been overlays in the
first place ?
Here is a patch for one place,
That patch I sent only works if font-lock is a current feature. I just
realized this on starting a new emacs. There must be a better way to clear
a buffer/region of all non-default face information.
Jack Vinson - - - [EMAIL PROTECTED] Sunderland, MA
WWW: "http://www.cis.upenn.edu/~vinson
MM> I've started using font-lock yesterday;
MM> and now bbdb starts behaving funnily, when mail reading, it asks
MM> (for every entry!)
MM> replace "Martin B. Maechler" by "Martin B. Maechler" ?
MM> (both are the same).
The problem is that bbdb is getting a fontified version of the nam
I've started using font-lock yesterday;
and now bbdb starts behaving funnily, when mail reading, it asks
(for every entry!)
replace "Martin B. Maechler" by "Martin B. Maechler" ?
(both are the same).
Ok, I am still using 1.49 [it always `worked'...]
But then,
looking in my sav
