Okay,
I've offically nailed BBDB-2.2 in CVS. Release notes, freshmeat
uploads, website changes, etc. are still in progress, but...
since I tagged it just before midnight, it's exactly two years after
the last BBDB release, which is the deadline I've been unofficially
trying to hit.
Release note
On January 14, [EMAIL PROTECTED] said:
> (ps - the docs say info-bbdb, not bbdb-info...)
Only in historically significant (!) places, as far as I can see...
Cheers,
Waider. Do correct me if I'm wrong.
--
[EMAIL PROTECTED] / Yes, it /is/ very personal of me.
I really need to reinstate the witty
Actually, looks like a simple modification to bbdb-com.el. This patch will
optionally allow mail-alias expansion during bbdb-complete-name.
RCS file: /cvsroot/bbdb/bbdb/lisp/bbdb-com.el,v
retrieving revision 1.90
diff -c -C0 -r1.90 bbdb-com.el
*** bbdb-com.el 2001/01/24 02:07:18 1.90
--- bb
I use eudc since I search both ldap and bbdb, but I bet the same sort
of advice could be applied directly to bbdb-complete-name:
(defadvice eudc-expand-inline (around check-aliases-too activate)
"If eudc-expand-inline doesn't find a match, check for a match in mail-aliases."
(condition-case n
Is there a way to make bbdb-complete-name also do expand-abbrev on
mail-aliases? Seems like I have hit CR or SP instead.
___
bbdb-info mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/bbdb-info
Ronan Waide wrote:
> Okay, I've patched this. I don't think it should fatal-error on this,
> either, just warn you, sit-for, and continue on its way. FITNR, as
> they say.
Yup. There are other things that would need to be improved in the
sound code. For instance, under XEmacs with sound
Nix <[EMAIL PROTECTED]> wrote:
> This is a client issue, not a server-side one. (Rare, really; most of
> the annoyances I get with CVS crop up on the server, where mortals
> cannot fix them. I've never had any problems with the BBDB repository,
> though.)
OK, I had done this before, but
