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
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
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 the
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 first
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 bugs ;)
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
when
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 net
