Re: add bbdb-mail-aliases to bbdb-insinuate-gnus?
On Thu May 22 2014 Eric Abrahamsen wrote: There is already a skeleton on savannah, volunteers welcome. I do request that contributors assign their copyright to the FSF (I believe you already have). I've seen that, but I guess by skeleton I meant not a texi file outline, but a general topic outline for the manual. It's harder to get started when you're staring at a blank page... But if that's what there is, that'll do as well. So far, I did not find the time to familiarize myself in more detail with writing a texi info manual. So up to now the skeleton is what it is. As I said, volunteers welcome. -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: add bbdb-mail-aliases to bbdb-insinuate-gnus?
On Tue May 20 2014 Eric Abrahamsen wrote: I don't know enough about the auto-update stuff to say. It never made a whole lot of sense to me, requiring both (bbdb-initialize 'gnus) and (bbdb-mua-auto-update-init 'gnus), because I can't really imagine wanting one but not the other. Are you proposing an equivalent: (bbdb-initialize 'gnus 'gnus-auto-update) I expect something like the following to be more common (bbdb-initialize 'gnus 'message-auto-update) This way the auto-update is all in all less aggressive. Or something like that? There are so many other options controlling how messages are scanned, it seems like you could leave out initializing the auto-update stuff entirely and just let users play with bbdb-mua-auto-update-p. As usual, I guess this is a matter of taste. How many people are using multiple MUAs? From BBDB's perspective everyone uses two, one for incoming and one for outgoing messages. Also, does anyone have a bbdb.texi file underway? If there was even a skeleton TOC in the repository, it would make it easier to start tossing in bits and pieces of documentation. There is already a skeleton on savannah, volunteers welcome. I do request that contributors assign their copyright to the FSF (I believe you already have). Roland -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: add bbdb-mail-aliases to bbdb-insinuate-gnus?
On Mon May 19 2014 Eric Abrahamsen wrote: For a year or more I've been mildly curious about why mail aliases didn't work in BBDB -- nothing ever expanded. I finally tried to figure out why, and realized you have to manually call `bbdb-mail-aliases' in order to make it work. It seems like this is something that should happen on (bbdb-initialize 'gnus), doesn't it? Inside `bbdb-insinuate-gnus' (or somewhere else appropriate) couldn't we check to see if any records have a mail-alias field, and automatically set up the mail aliases, if so? I'd be happy to provide a patch. Thanks, I have never thought about this. Already with BBDB v2 it was necessary to initialize mail-aliases via a function to be put into mail-setup-hook (then possily called differently from bbdb-mail-aliases). I guess this can be handled by bbdb-initialize. But this feature is really separate from the other ones handled by bbdb-initialize and I am hesitant to provide packaged solutions where some initialization intends to address several unrelated issues. So probably this should be handled by a separate arg for bbdb-initialize. While there are lots of different and unrelated features that can be initialized, it is probably good to provide one common way of initializing them (and also documenting them in the docstring of bbdb-initialize). So it might also be good to make bbdb-mua-auto-update-init obsolete, but instead handle all these features by different args for bbdb-initialize. Roland -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
add bbdb-mail-aliases to bbdb-insinuate-gnus?
For a year or more I've been mildly curious about why mail aliases didn't work in BBDB -- nothing ever expanded. I finally tried to figure out why, and realized you have to manually call `bbdb-mail-aliases' in order to make it work. It seems like this is something that should happen on (bbdb-initialize 'gnus), doesn't it? Inside `bbdb-insinuate-gnus' (or somewhere else appropriate) couldn't we check to see if any records have a mail-alias field, and automatically set up the mail aliases, if so? I'd be happy to provide a patch. Eric -- Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free. http://p.sf.net/sfu/SauceLabs ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
