Re: bbdb-popup-target-window-size (Re: BBDB 3.x documentation)

2011-02-04 Thread Stefan Monnier
Well, my recent discovery was that the variable name change bbdb-popup-target-lines - bbdb-popup-window-size in BBDB 3.x. They seem to do the same thing (i.e. setting the target number of lines for the bbdb-popup window). The default value was 5 but is now 0.5. You are right. I guess the

Re: bbdb-popup-target-window-size (Re: BBDB 3.x documentation)

2011-02-04 Thread Roland Winkler
On Fri Feb 4 2011 Stefan Monnier wrote: You are right. I guess the change of the default happened when I added the code to use not only absolute line numbers but fractions of the window hight. In general, my personal preference is to use the latter. I'll be happy to go back to the old

Re: bbdb-popup-target-window-size (Re: BBDB 3.x documentation)

2011-02-04 Thread Johnny
Roland Winkler wink...@gnu.org writes: The doc string of bbdb-pop-up-window-size says: The doc strings (that's the ones in the lisp code, right?) are good for BBDB 3.x. It's just that I am used to read the info files to get up to speed, being a lisp neophyte. But it's a good learning experience!

bbdb-popup-target-window-size (Re: BBDB 3.x documentation)

2011-02-02 Thread Roland Winkler
On Wed Feb 2 2011 Johnny wrote: Well, my recent discovery was that the variable name change bbdb-popup-target-lines - bbdb-popup-window-size in BBDB 3.x. They seem to do the same thing (i.e. setting the target number of lines for the bbdb-popup window). The default value was 5 but is now 0.5.

bbdb/gnus-show-sender (Re: BBDB 3.x documentation)

2011-02-02 Thread Roland Winkler
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

BBDB 3.x documentation

2011-01-29 Thread Johnny
As I am occasionaly fiddling around with the new BBDB (3.02) to get a nice set-up and using the old documentation to get around, every now and then I encounter the changes in e.g. parameter names. I guess the new version will reside on Savannah also in the future (and not Sourceforge that seems to