Description of problem: If I try to customize the bbdb/mail-auto-create-p variable to refer to a function, using Customize, emacs prints an error in the minibuffer and doesn't let me. Version-Release number of selected component (if applicable): emacs-bbdb-2.35-3.fc12.noarch How reproducible: Always Steps to Reproduce: 1. emacs -Q 2. (require 'bbdb) 3. In the Options menu, choose Customize Emacs -> Specific Option -> bbdb/mail-auto-create-p 4. Click Value Menu, and choose Create with function Actual results: Minibuffer displays: read: Symbol's function definition is void: bbdb- Expected results: Customize should offer to let me set a function Additional info: emacs-23.1-6.fc12.i686
Can you get the full error message (not truncated) from the *Messages* buffer? Thanks.
It's just read: Symbol's function definition is void: bbdb-
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still present in emacs-bbdb-2.35-4.fc13.noarch.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still present in emacs-bbdb-2.35-5.fc15.noarch.
Still present in emacs-bbdb-2.35-8.fc17.noarch. The steps to reproduce need to be changed - add: (add-to-list 'load-path "/usr/share/emacs/site-lisp/bbdb") so that emacs can find it.
And also present in emacs-bbdb-2.35-10.fc18.noarch apparently. I'll have a look and see if I can understand what is going on.
To me it looks like an upstreams bug in the code. To begin with, I've reported it: https://savannah.nongnu.org/bugs/index.php?38178
Upstreams doesn't seem interested in BBDB 2, only in BBDB 3. I'll try to make a patch instead.
emacs-bbdb-2.35-11.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/emacs-bbdb-2.35-11.fc18
emacs-bbdb-2.35-9.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/emacs-bbdb-2.35-9.fc17
Package emacs-bbdb-2.35-9.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing emacs-bbdb-2.35-9.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-1766/emacs-bbdb-2.35-9.fc17 then log in and leave karma (feedback).
emacs-bbdb-2.35-9.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
emacs-bbdb-2.35-11.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.