Ok, so I have reverted to bbdb 2.35 to test the ';' (bbdb/gnus-edit-notes) functionality, and using this function adds the sender to the database if not already present, as explained in the info files.
This function is broken in bbdb 3.02 as the ';' does not add the sender to the database. Cross-posting (let me know if this is wrong) to the gnus mailing list, if some experience Gus user has resolved this. Previous said on this topic as below... "Roland Winkler" <wink...@gnu.org> writes: > On Wed Feb 2 2011 Johnny wrote: >> "Roland Winkler" <wink...@gnu.org> writes: >> >> Further, I don't understand how to get the bbdb/gnus-show-sender to add >> unknown addresses; > [snip] > >> However, browsing the lisp code, I assume that the following is actually >> invoked (?) which seems to simply return nothing if the sender is not >> found, as opposed to adding the sender: >> >> > (defun bbdb/gnus-summary-sender-in-bbdb (header) >> > "Given a Gnus message header, return a mark if the poster is in the BBDB, >> > \" \" otherwise. The mark itself is the value of the field indicated >> > by `bbdb/gnus-message-marker-field' (`mark-char' by default) if the >> indicated field >> > is in the poster's record, and `bbdb/gnus-summary-known-poster-mark' >> otherwise." >> > >> >> Is there something I am missing here, as I believe there ought to be a >> fast and easy method to do exactly what is stated in the manual; >> i.e. look up an address, and if it doesn't exist, volunteer to add >> it. > > The generic command for this is now bbdb-mua-display-sender. > In Gnus, BBDB binds this command to ";". > > Unfortunately I am not a more experienced Gnus user, and there is a > nasty technicality about keybindings in Gnus that I do not yet > understand myself: > > While bbdb-insinuate-gnus contains the line > > (define-key gnus-summary-mode-map ":" 'bbdb-mua-display-sender) > > the command `gnus-article-read-summary-keys provides an additional > wrapper for bbdb-mua-display-sender which restores the windwo > configuration if this command is invoked from within a Gnus > *Article* buffer. So the command bbdb-mua-display-sender has not > quite the intended effect of displaying a BBDB window for the record > matching the sender of a Gnus message. > > Currently, the command bbdb-mua-display-sender only works as > intended from within a Gnus *Summary* buffer. > > Comments from more experienced Gnus users are appreciated. > Possibly, we should continue this thread on the Gnus mailing list. > > Roland -- Johnny ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
