Re: grave completion bug in bbdb 2.2

2001-02-21 Thread Ronan Waide
On February 21, [EMAIL PROTECTED] said: > Oh come now, that's not a very fair comparison. The functionality of > the completion function is really quite simple. It was just augmented > repeatedly without breaking out routines, until is is now an > unmanageable mess. It needs to be hacked with t

Re: grave completion bug in bbdb 2.2

2001-02-21 Thread Barak Pearlmutter
Oh come now, that's not a very fair comparison. The functionality of the completion function is really quite simple. It was just augmented repeatedly without breaking out routines, until is is now an unmanageable mess. It needs to be hacked with the byte saber. One function that takes a partia

Re: grave completion bug in bbdb 2.2

2001-02-21 Thread Ronan Waide
On February 20, [EMAIL PROTECTED] said: > more and more email goes to the non-primary address. And the bbdb > maintainers cannot even fix it, because it's a horrble ten-page mess > of vaguely documented gratuitously complex side-effectful elisp crud > that everyone is too scared to take a serious

Re: grave completion bug in bbdb 2.2

2001-02-20 Thread Barak Pearlmutter
The bbdb-complete-name code is 235 lines long. It is very hairy. And gratuitously so! It is not speed critical. It would be very easy to break it up into nice little subroutines. There could be a separate function for cycling, called by the main routine when the user seems to want to cycle.

Re: grave completion bug in bbdb 2.2

2001-02-13 Thread Robert Fenk
On Saturday, February 10 2001 15:53:05, Patrick Campbell-Preston wrote: [...] > The bug still happens for me, even with today's tarball from Ronan's > page, but not so repeatably - it seems to happen only the first time I > complete a particular name. Are you sure the fix is good? As I noticed j

Re: grave completion bug in bbdb 2.2

2001-02-10 Thread Benjamin Rutt
Patrick Campbell-Preston <[EMAIL PROTECTED]> writes: > The bug still happens for me, even with today's tarball from Ronan's > page, but not so repeatably - it seems to happen only the first time I > complete a particular name. Are you sure the fix is good? It still happens for me also. I just

Re: grave completion bug in bbdb 2.2

2001-02-10 Thread Patrick Campbell-Preston
> Robert Fenk wrote: > > > Ahh it's a GNU Emacs problem. > > A fix is in CVS now. > > Thanks - will download the nightly tarball again tomorrow. The bug still happens for me, even with today's tarball from Ronan's page, but not so repeatably - it seems to happen only the first time I complete

Re: grave completion bug in bbdb 2.2

2001-02-08 Thread Robert Fenk
Patrick Campbell-Preston wrote: [...] > Was it a real bug in GNU Emacs which you have had to work > around, or just another of those annoying > incompatibilities? Both. It was a real bug which did not show up in xemacs, since the hash tables used for GNU/Xemacs return different results. The firs

Re: grave completion bug in bbdb 2.2,Re: grave completion bug in bbdb 2.2

2001-02-07 Thread Patrick Campbell-Preston
Robert Fenk wrote: > Ahh it's a GNU Emacs problem. > A fix is in CVS now. Thanks - will download the nightly tarball again tomorrow. > Not only the BBDB version but also the Emacs version and > sometime the OS is making problems, so it is a good idea to > report all of these when reporting bug

Re: grave completion bug in bbdb 2.2,Re: grave completion bug in bbdb 2.2

2001-02-07 Thread Robert Fenk
On Tuesday, February 6 2001 22:31:40, Patrick Campbell-Preston wrote: [...] > I've downloaded the latest CVS version via Ronan's bbdb page, and > verified that I am able to reproduce the bug with it, with the simple > .bbdb described above and nothing in my .emacs apart from loading the > bbdb and

Re: grave completion bug in bbdb 2.2

2001-02-06 Thread Benjamin Rutt
Robert Fenk <[EMAIL PROTECTED]> writes: > I am not able to reproduce this with the current CVS > version. Is there anyone else using the current CVS > version who is able to reproduce this? yes, I am able to reproduce this with the current CVS version. For some records, a record with multiple

Re: grave completion bug in bbdb 2.2

2001-02-06 Thread Patrick Campbell-Preston
Robert, > On Monday, February 5 2001 23:51:15, Patrick Campbell-Preston wrote: > > I've found a serious bug in BBDB version 2.2 ($Date: 2001/01/24 > > 23:14:00 $) - it seems to be getting completion wrong. Using either a > > version 5 or version 6 database with the following single entry: > >

Re: grave completion bug in bbdb 2.2

2001-02-06 Thread Patrick Campbell-Preston
Robert, > [...] > > Can I be the first one to be too late to suggest that overloading > > bbdb-complete-name with the cycling through nets functionality is a > > really dumb idea? > Why is it dump? IMHO it is natural and it should cycle only > when the completion is finished. Let's agree to

Re: grave completion bug in bbdb 2.2

2001-02-06 Thread Robert Fenk
On Monday, February 5 2001 23:51:15, Patrick Campbell-Preston wrote: [...] > Can I be the first one to be too late to suggest that overloading > bbdb-complete-name with the cycling through nets functionality is a > really dumb idea? Why is it dump? IMHO it is natural and it should cycle only wh

Re: grave completion bug in bbdb 2.2

2001-02-06 Thread Robert Fenk
On Monday, February 5 2001 23:51:15, Patrick Campbell-Preston wrote: > I've found a serious bug in BBDB version 2.2 ($Date: 2001/01/24 > 23:14:00 $) - it seems to be getting completion wrong. Using either a > version 5 or version 6 database with the following single entry: > > foo fum >