Completing records with organization field
Hi, I got some weird behavior in bbdb3: When I try to complete entries without organization everything is normal, I get FirstName LastName mail , but on entries that have an organization set I just get mail . I don't suppose this is a feature? Or did I miss some customization variable? BBDB version 3.02 ($Date: 2011/10/10 18:04:34 $) No Gnus v0.18 GNU Emacs 24.0.91.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.8) -- Philipp Haselwarter -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Completing records with organization field
On Sun Nov 20 2011 Philipp Haselwarter wrote: I got some weird behavior in bbdb3: When I try to complete entries without organization everything is normal, I get FirstName LastName mail , but on entries that have an organization set I just get mail . I don't suppose this is a feature? Or did I miss some customization variable? I guess you need to be more specific here. What command do you execute under what circumstances? What are your BBDB settings? If the command was bbdb-complete-mail, I do not quite see how you could get a mail address not surrounded by (Your mail says that instead you had NO-BREAK SPACEs, which is yet more strange. BBDB does not deal with the NO-BREAK SPACE character anywhere.) Roland -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Completing records with organization field
Roland Winkler wink...@gnu.org writes: On Sun Nov 20 2011 Philipp Haselwarter wrote: I got some weird behavior in bbdb3: When I try to complete entries without organization everything is normal, I get FirstName LastName mail , but on entries that have an organization set I just get mail . I don't suppose this is a feature? Or did I miss some customization variable? I guess you need to be more specific here. What command do you execute under what circumstances? What are your BBDB settings? If the command was bbdb-complete-mail, I do not quite see how you could get a mail address not surrounded by (Your mail says that instead you had NO-BREAK SPACEs, which is yet more strange. BBDB does not deal with the NO-BREAK SPACE character anywhere.) Roland I put in the NO-BREAK SPACE to avoid formatting quirks and ambiguity around the quotation marks, didn't actually avoid confusion, huh? :) I attached an example bbdb file with a few entries and a recipe to reproduce the behavior. The steps are: --8---cut here---start-8--- mkdir fakehome # install bbdb into fakehome/lisp cp .bbdb recipe.el fakehome cd fakehome HOME=$(pwd) emacs -Q -l recipe.el --8---cut here---end---8--- Most of the contacts offer just the mail address on as completion: --8---cut here---start-8--- In this buffer, type RET to select the completion near point. Possible completions are: alice@mail.org james.sm...@mail.org Emmanuel Leblanc manu.lebl...@mail.com emmanuel@uni.frAnon Ymos a...@ymos.com jane@mail.org --8---cut here---end---8--- Tested with GNU Emacs 24.0.91.1 and 23.3.1 -- Philipp Haselwarter .bbdb Description: Binary data recipe.el Description: application/emacs-lisp -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Manual for BBDB 3
Hi, I'm new to BBDB and confused by which manual to use for which version. I currently use BBDB version 3.02 ($Date: 2011/10/10 18:04:34 $) and it seems there is no info manual included and the only manual I could find is at: http://bbdb.sourceforge.net/bbdb.html and I can't make out which parts of the manual are still up to date. Is there an explicit manual for BBDB3 or is the old one still approriate? Can info files be distributed with BBDB3? I think it would make live easier for users that have no previous exposure to BBDB. Cheers, Philipp -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Manual for BBDB 3
Philipp Möller bootsare...@googlemail.com writes: I'm new to BBDB and confused by which manual to use for which version. I currently use BBDB version 3.02 ($Date: 2011/10/10 18:04:34 $) and it seems there is no info manual included and the only manual I could find is at: http://bbdb.sourceforge.net/bbdb.html and I can't make out which parts of the manual are still up to date. From interactions on this list, it appears that most-to-all of the old manual is invalid for BBDB3. Is there an explicit manual for BBDB3 or is the old one still approriate? As far as I'm aware there is no manual for BBDD3. I'll be glad to help proofread if you want to write one. :) -- http://www.wistly.net -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Completing records with organization field
On Sun Nov 20 2011 Philipp Haselwarter wrote: When I try to complete entries without organization everything is normal, I get FirstName LastName mail , but on entries that have an organization set I just get mail . I attached an example bbdb file with a few entries and a recipe to reproduce the behavior. Possible completions are: alice@mail.org james.sm...@mail.org Emmanuel Leblanc manu.lebl...@mail.com emmanuel@uni.frAnon Ymos a...@ymos.com jane@mail.org I am sorry, this has nothing to do with the organization field. For example, Alice Doe does not have an organization field. What matters is that some names are also part of the email address. It seems you want bbdb-mail-allow-redundancy set to t. Actually, I do not know why this variable's default is nil (well, I guess its default was always nil...) Would anybody mind if I set it to t? I guess that's more often matching the users' expectations. Roland -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Manual for BBDB 3
Carson Chittom car...@wistly.net writes: Philipp Möller bootsare...@googlemail.com writes: I'm new to BBDB and confused by which manual to use for which version. I currently use BBDB version 3.02 ($Date: 2011/10/10 18:04:34 $) and it seems there is no info manual included and the only manual I could find is at: http://bbdb.sourceforge.net/bbdb.html and I can't make out which parts of the manual are still up to date. From interactions on this list, it appears that most-to-all of the old manual is invalid for BBDB3. So for now it is just looking at source and figuring things out. Is there an explicit manual for BBDB3 or is the old one still approriate? As far as I'm aware there is no manual for BBDD3. I'll be glad to help proofread if you want to write one. :) If someone could provide an outline of main features it would be a good start. Is https://github.com/barak/bbdb3 the right place to fork and send pull requests? Philipp -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Completing records with organization field
On Sun Nov 20 2011 Roland Winkler wrote: It seems you want bbdb-mail-allow-redundancy set to t. Actually, I do not know why this variable's default is nil (well, I guess its default was always nil...) Would anybody mind if I set it to t? I guess that's more often matching the users' expectations. Actually, I am yet more tempted to replace this variable by bbdb-mail-avoid-redundancy as currently bbdb-mail-allow-redundancy supports not only nil and t, but also mail-only -- which is exactly the opposite you might expect from bbdb-mail-allow-redundancy. Roland -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Completing records with organization field
Roland Winkler wink...@gnu.org writes: On Sun Nov 20 2011 Philipp Haselwarter wrote: When I try to complete entries without organization everything is normal, I get FirstName LastName mail , but on entries that have an organization set I just get mail . I attached an example bbdb file with a few entries and a recipe to reproduce the behavior. Possible completions are: alice@mail.org james.sm...@mail.org Emmanuel Leblanc manu.lebl...@mail.com emmanuel@uni.frAnon Ymos a...@ymos.com jane@mail.org I am sorry, this has nothing to do with the organization field. Yea, I saw that… For example, Alice Doe does not have an organization field. What matters is that some names are also part of the email address. It seems you want bbdb-mail-allow-redundancy set to t. That does precisely what I want! Actually, I do not know why this variable's default is nil (well, I guess its default was always nil...) Would anybody mind if I set it to t? I guess that's more often matching the users' expectations. Roland I'd strongly recommend changing the default, the way it is now is highly counter-intuitive (for me) and as often, it's hard to find the right option if you don't know what you're looking for (in my case the only obvious difference between the contacts the organization). thanks, -- Philipp Haselwarter -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Manual for BBDB 3
Philipp Moeller bootsare...@googlemail.com writes: Carson Chittom car...@wistly.net writes: Philipp Möller bootsare...@googlemail.com writes: I'm new to BBDB and confused by which manual to use for which version. From interactions on this list, it appears that most-to-all of the old manual is invalid for BBDB3. So for now it is just looking at source and figuring things out. Please don't disregard the old manual completely, but read with caution! I have learned to use BBDB 3 pretty much from the old manual, so it's certainly a reasonable place to start. There are some breaking changes in variable names, and that's where looking at the docstrings / source or eventually the mailing list comes in. If you have the time, keep notes of the changes as you learn; these will be useful for updating the manual. I asked about this previously, but it seems an update is (understandably) not on top of the todo list. I guess if the info files are included in git, maybe someone else than the main developer(s?) could work on it? I wouldn't mind trying to help, but have limited experience. The only note (unfortunately) I have kept is below. , | ;(add-hook 'message-setup-hook 'bbdb-define-all-aliases) ; BBDB 2.35 | (add-hook 'message-setup-hook 'bbdb-mail-aliases) ; BBDB 3.x ` Also, I think the set-up has changed; see a recent message on the list on this. -- Johnny -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
[BBDB] ChangeLog 2011-11-20
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 you set variables in your init file that are not used anymore by BBDB (so that they are not documented anymore either), these variables will be displayed by bbdb-undocumented-variables. (Unfortunately, this fails for outdated BBDB variables that are set via your personal `custom-file'. Let me know if you know a better solution for this.) On Wed Oct 26 2011 Carson Chittom wrote: If ~/.bbdb is nonexistent, M-x bbdb-create creates it improperly such that it requires a manual edit. This should be fixed now. On Sat Oct 29 2011 Peter Münster wrote: Finally I understand: `bbdb-mua-display-*' does not only *display* records, but can also update them, depending on `bbdb-mua-update-interactive-p'. I've replaced `bbdb-mua-edit-notes-*' by `bbdb-mua-display-records' and everything is fine now! Oh well, this is one of the things that should go into a proper documentation (= info). The updated README file is a starting point. On Fri Nov 4 2011 Ivan Kanis wrote: Finally found some time to work on bbdb. Here is patch that implements picture of people's mug shot. I tried to clean up this patch - use the same names and words that are used by the functions doing the real work (and let them do as much work as possible) - see the new variables bbdb-image, bbdb-image-path, and bbdb-image-suffixes. (I did not want to put these things into a new file which necessarily would be required by one of BBDB's core function in bbdb.el.) On Sat Nov 19 2011 Ivan Kanis wrote: OK I found the fix, the variable bbdb-complete-name-allow-cycling got renamed to bbdb-complete-mail-allow-cycling. Setting the former to t got me the expected behavior. See above for the new command bbdb-undocumented-variables. 2011-11-20 Roland Winkler wink...@gnu.org * README: Updated. * lisp/bbdb.el (bbdb-message-try-all-headers) (bbdb-user-mail-address-re): Clarify doc string. (bbdb-defstruct): Do not update bbdb-mail-aliases-need-rebuilt. (bbdb-record-set-note): Update bbdb-mail-aliases-need-rebuilt. (bbdb-record-set-name): Update name in cache and hash. (bbdb-record-unset-name): Removed (obsolete). (bbdb-hash-update): New function. (bbdb-record-set-field): Use it. (bbdb-records): Initiate variable bbdb-records. (bbdb-parse-internal): Use bbdb-goto-first-record. (bbdb-goto-first-record): Move backward only if we found a first record. * lisp/bbdb-com.el (bbdb-insert-field) (bbdb-delete-field-or-record): Use bbdb-record-set-field. (bbdb-edit-field): New optional arg value. Handle affix, organization, mail, aka, and note fields directly. (bbdb-record-edit-affix, bbdb-record-edit-organziation) (bbdb-record-edit-mail, bbdb-record-edit-aka) (bbdb-record-edit-note): Removed. * lisp/bbdb.el (bbdb-mail-avoid-redundancy) Renamed from bbdb-mail-allow-redundancy. * lisp/bbdb-com.el (bbdb-dwim-mail): Update it accordingly. * lisp/bbdb.el (bbdb-update-records-p): Change default to less agressive `search'. (bbdb-mua-auto-update-p): New variable * lisp/bbdb-mua.el (bbdb-mua-auto-update): Use it. (bbdb-update-records): Resolve arg update-p up to two times. * lisp/bbdb-message.el (bbdb/message-update-records-p) * lisp/bbdb-rmail.el (bbdb/rmail-update-records-p) * lisp/bbdb-gnus.el (bbdb/gnus-update-records-p) * lisp/bbdb-mhe.el (bbdb/mh-update-records-p) * lisp/bbdb-vm.el (bbdb/vm-update-records-p): Doc fix. * lisp/bbdb-mua.el (bbdb-annotate-record): Convert annotation into list if field is affix, organization, mail or aka. (bbdb-mua-edit-field-interactive): New function. (bbdb-mua-edit-field): New command. (bbdb-mua-edit-field-sender, bbdb-mua-edit-field-recipients): Use it. * lisp/bbdb.el (bbdb-image, bbdb-image-path, bbdb-image-suffixes): New variables. (bbdb-display-name-organization): Use them to display images for BBDB records. Suggested by Ivan Kanis ap...@kanis.fr. * lisp/bbdb-migrate.el (bbdb-undocumented-variables): New command. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net
Re: [BBDB] ChangeLog 2011-11-20
* 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 information about the replacements for the obsolete variables. as I said before, TRT is to use define-obsolete-function-alias define-obsolete-variable-alias All variables in BBDB 3 now have a doc string. So if you set variables in your init file that are not used anymore by BBDB (so that they are not documented anymore either), these variables will be displayed by bbdb-undocumented-variables. (Unfortunately, this fails for outdated BBDB variables that are set via your personal `custom-file'. Let me know if you know a better solution for this.) just use apropos-internal and iterate over the symbols it returns, looking for those with 'custom properties set but no doc string. however, this is _not_ the right approach (see above) -- Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11004000 http://honestreporting.com http://www.PetitionOnline.com/tap12009/ http://camera.org http://jihadwatch.org http://thereligionofpeace.com You can have it good, soon or cheap. Pick two... -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: [BBDB] ChangeLog 2011-11-20
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 latest patch: In BBDB v2 there was (defcustom bbdb-dwim-net-address-allow-redundancy nil *Non-nil means always use full name when sending mail, even if same as net. :group 'bbdb :type '(choice (const :tag Disallow redundancy nil) (const :tag Return only the net 'netonly) (const :tag Allow redundancy t))) See the undocumented option `netonly' meaning: Never use the full name but only the net address - which was not quite matching intuitive expectations for a variable with this name / this docstring. So now there is (defcustom bbdb-mail-avoid-redundancy nil Mail address to use for BBDB records when sending mail. If non-nil do not use full name in mail address when same as mail. If value is mail-only never use full name. :group 'bbdb-sendmail :type '(choice (const :tag Allow redundancy nil) (const :tag Never use full name 'mail-only) (const :tag Avoid redundancy t))) define-obsolete-variable-alias would not be too helpful here. Nobody requires you to switch to BBDB v3. But if you want to use it, at some point you will have to work your way through functions and variables, which are different from the old ones (see also the updated README file for more important examples regarding BBDB's MUA interfaces, where concepts have changed quite significantly). Roland -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Manual for BBDB 3
On Sun Nov 20 2011 Philipp Moeller wrote: So for now it is just looking at source and figuring things out. I am sorry, the updates in BBDB v3 are still work in progress. The code itself is already fairly mature by now, but the rest (documentation and installation support) is stil lacking behind. Volunteers welcome :-) For someone new to BBDB, the most important piece of source code to look into is certainly the beginning of bbdb.el with all the user variables for BBDB. I tried to arrange them in a logical order. Also, the menu bar gives you a fairly complete overview of the commands available inside the *BBDB* buffer. (For many emacs modes the menu bar comes handy for this.) If someone could provide an outline of main features it would be a good start. For getting an idea of what can be done with BBDB, the old info manual could still be usueful, though the implementation of these ideas has changed quite significantly. Is https://github.com/barak/bbdb3 the right place to fork and send pull requests? I do not know to what extent Barak keeps his mirror up to date. BBDB is available at http://savannah.nongnu.org/projects/bbdb/ To check it out, use git clone git://git.savannah.nongnu.org/bbdb.git Roland -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
