recipient name completion

recipient name completion

[Sébastien Kirche]

Hi,

I have played a little with my new (from NoGnus cvs) message-expand-name and
eudc/ldap configuration and I have a problem.

Both  eudc-expand-inline  and bbdb-complete-name  are  functional if  called
manually  (e.g.  in the  scratch  buffer).  If  I understand  correctly  the
message-expand-name defun, the cond statement should call the both functions
(message-expand-name-databases  value is (bbdb  eudc)) but  it seems  that I
cannot complete anymore my contacts from BBDB.

Also  maybe one  can define  some kind  of priority  to call  the completion
functions, as  for the moment  if eudc-expand-inline completes first  and we
are looking for  someone that is in  BBDB we wont find him.  It could follow
the order of message-expand-name-databases definition.

I have looked into the cvs ToDo  but it does not seem to be mentioned. Maybe
I could make a proposal ?

Regards.

-- 
Sébastien Kirche

Re: recipient name completion

[Sébastien Kirche]

Le 30 Mar 2005, Sébastien Kirche vraute :

> Both  eudc-expand-inline and bbdb-complete-name  are functional  if called
> manually  (e.g. in  the scratch  buffer).  If I  understand correctly  the
> message-expand-name  defun,  the  cond  statement  should  call  the  both
> functions  (message-expand-name-databases  value is  (bbdb  eudc)) but  it
> seems that I cannot complete anymore my contacts from BBDB.

Well I made a mistake about the lisp  code : it is normal that the bbdb part
is  not   called  as  the  first   form  of  cond  (ie:   (and  (memq  'eudc
message-expand-name-databases  ) (boundp  'eudc-protocol)  eudc-protocol) is
non nil...

I think I need some modification of message-expand-name for my goal...

-- 
Sébastien Kirche