On 26 Nov, 2011, at 8:28 am, Roland Winkler wrote:
On Thu Nov 24 2011 Stefan Monnier wrote:
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
On Sat Nov 26 2011 Philip Hudson wrote:
Maybe I'll start with code doco, just standards compliance and
formatting and filling in missing docstrings where I can. That'll help
build the domain knowledge. Patches to the list, right?
You'd like to provide documentation patches that are
* Roland Winkler jvax...@tah.bet [2011-11-20 23:13:36 -0600]:
On Sun Nov 20 2011 Sam Steingold wrote:
as I said before, TRT is to use define-obsolete-function-alias
define-obsolete-variable-alias
This would require a simple one-to-one correspondence between
function and variable names in
The README file now gives an overview on how BBDB v3 interfaces with MUAs.
The new command bbdb-undocumented-variables might help you to
identify outdated variables. This displays a list of all
undocumented variables in the bbdb- name space.
All variables in BBDB 3 now have a doc string. So if
* Roland Winkler jvax...@tah.bet [2011-11-20 17:52:40 -0600]:
The new command bbdb-undocumented-variables might help you to
identify outdated variables. This displays a list of all
undocumented variables in the bbdb- name space.
this is a good start!
still, this does not give me any
On Sun Nov 20 2011 Sam Steingold wrote:
as I said before, TRT is to use define-obsolete-function-alias
define-obsolete-variable-alias
This would require a simple one-to-one correspondence between
function and variable names in BBDB v2 and v3 which is NOT the case.
A simple example from the
