On Thu Nov 24 2011 Stefan Monnier wrote:
> > (defcustom bbdb-dwim-net-address-allow-redundancy nil
> [...]
> > So now there is
> > (defcustom bbdb-mail-avoid-redundancy nil
> [...]
> > define-obsolete-variable-alias would not be too helpful here.
>
> Agreed. But it would make a lot of sense to do
>
> (defcustom bbdb-mail-avoid-redundancy
> (if (boundp 'bbdb-mail-avoid-redundancy)
> <blabla))
Looks like a typo. You probably meant
(if (boundp 'bbdb-dwim-net-address-allow-redundancy)
<blabla))
I agree that some compatibility mode could be useful. But I am
hesitant to clutter the new code with it. If at all, I'd much prefer
to put it into some kind of after-load form kept separate from the
new code.
Yet the main thing for me is: My time is limited for such things; I
need to set up priorities. Currently I find it more important to
have a more coherent documentation of the new code including a
proper up-to-date info manual. (Well, in the long run, a proper
release wouldn't be bad either....)
If anybody else wants to work on this, please go ahead. In my
opinion, the EmacsWiki UpgradeBBDB put up by Leo is a good starting
point
http://www.emacswiki.org/emacs/UpgradeBBDB
Please, contribute to it if you find anything noteworthy.
Roland
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
