Re: BBDB 3.0

2011-02-13 Thread Roland Winkler
On Sun Feb 13 2011 Antoine Levitt wrote: > 13/02/11 14:12, Roland Winkler > > On Sun Feb 13 2011 Antoine Levitt wrote: > >> It does work, but this enables a pop-up window, which I don't want. With > >> this init, setting bbdb-message-pop-up to nil also disables the > >> noticing, is that normal? >

Re: BBDB 3.0

2011-02-13 Thread Roland Winkler
On Sun Feb 13 2011 Antoine Levitt wrote: > > I guess from your perspective bbdb-mua-pop-up-bbdb-buffer is, first > > of all, a misnomer. The main action is hidden in > > bbdb-mua-update-records. -- I'll look into this. > > Yes. Maybe there should be two separate functions added to the hook, one >

Re: bbdb-complete-name return value

2011-02-13 Thread Ted Zlatanov
On Sat, 12 Feb 2011 11:47:40 -0600 "Roland Winkler" wrote: RW> So I would suggest the following "BBDB task sheet" for a generic RW> completion algorithm that could possibly replace the current code in RW> bbdb-complete-mail: RW> (1) Substring completion needs to have some understanding of the R

Re: bbdb-complete-name return value

2011-02-13 Thread Roland Winkler
On Sun Feb 13 2011 Ted Zlatanov wrote: > I would approach this as a scoring problem. Let BBDB have a score for > each address (so multiples can be in a record), defaulting to 0. [snip] > And so on, but the important thing is to have scoring rules and base > scores. The user should be able to cust

Re: bbdb-complete-name return value

2011-02-13 Thread Stefan Monnier
[ Apparently my messages don't make it to the list because the list does not accept messages from the Gmane gateway. ] > - One problem with completion in BBDB can be that if the algorithm > isn't optimized enough for its particular problem, it happens too > easily that the algorithm offers too

Re: bbdb-complete-name return value

2011-02-13 Thread Stefan Monnier
>> IMO the cycling should only be based on scores. That would, I think, >> accomplish all your items and produce less "DWIM but that's not it." Currently, the cycling code is fairly naive and it uses a fixed ordering based on string length (shorter first). Patches to make it more customizable (b