Re: [BBDB] ChangeLog 2012-07-06
Sam Steingold s...@gnu.org writes: Can you explain why you want to override your choice for bbdb-message-all-addresses in this function? when I try to edit a field when bbdb-message-all-addresses is t, the record being edited is the first record displayed, not the record of the sender. I gather you think that's wrong, even though it is what you requested. Apparently you want to set bbdb-message-all-addresses to nil, not t. Why did you set it to t? It defaults to nil, so you set it deliberately. -- -- Stephe -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: Why V3
On Sat Jul 7 2012 Johnny wrote: By now, unless someone on this list brings up problems with BBDB v3 that remained unnoticed so far, I do not have plans to further modify the code of BBDB (except for fixing docstrings that could still be buggy / incomplete). In particular, I do not want to introduce any additional incompatible changes beyond the ones present in the current code. I would really like to see the compatibility with lookout.el and csv.el to be restored, if possible. This is the only way I see now for contacts import/export with Outlook, unless on a Windows machine. [1] [2] You are right! I believe there are various add-ons to BBDB including and beyond lookout.el and csv.el that have not yet been properly ported to BBDB 3. When I wrote the above, I had in mind the core functions of BBDB as implemented in bbdb.el, bbdb-com.el and bbdb-mua.el. Add-ons to BBDB should be able to rely on these core functions once BBDB 3 is released. (There is a small but nonzero probability that updating one or the other BBDB add-on reveals that some core function should have been implemented differently. -- Oh well, I do not know all the add-ons so well, and only a regular user of an add-on might notice certain things. So that's really where I would appreciate input from the BBDB user community.) Roland -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
bbdb-mua-edit-field and friends (was: [BBDB] ChangeLog 2012-07-06)
When I looked at the code once more, I realized an annoying inconsistency: bbdb-mua-edit-field and friends do not use the default user variable bbdb-mua-update-interactive-p used by commands such as bbdb-mua-display-records. Currently they simply ignore the optional arg update-p so that the mua-specific fallbacks such as bbdb/gnus-update-records-p are used by these commands. I consider this a suboptimal solution. It would be more consistent if these commands obeyed bbdb-mua-update-interactive-p just like the other MUA commands. Yet the problem lies in the usage of the prefix arg: Commands such as bbdb-mua-display-records can use their prefix arg for the two alternatives implemented by bbdb-mua-update-interactive-p. Commands such as bbdb-mua-edit-field use their prefix arg for something else. So I can think of two possible strategies: (1) bbdb-mua-edit-field and friends use the no-prefix value of bbdb-mua-update-interactive-p. (2) All MUA commands use a separate prefix key for the two alternatives provided by bbdb-mua-update-interactive-p. This would be similar to the prefix keys `*' and `+' in the *BBDB* buffer. Then the different MUA commands can use the normal prefix arg for whatever they like without a conflict with bbdb-mua-update-interactive-p. Here a problem is finding a suitable key: The *BBDB* buffer has its own keymap so that there are many keys available for such a feature. In the MUA buffers, the key bindings for the MUA commands can use only those keys that are not used for anything else. Thoughts? Comments? Other suggestions? Roland -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
[BBDB] ChangeLog 2012-07-08
On Sat Jul 7 2012 Sam Steingold wrote: when I try to edit a field when bbdb-message-all-addresses is t, the record being edited is the first record displayed, not the record of the sender. The patch below should fix part of your problem by making the order of records more meaningful. 2012-07-08 Roland Winkler wink...@gnu.org * lisp/bbdb-mua.el (bbdb-update-records): Make records a list ordered like address-list. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: [BBDB] ChangeLog 2012-07-06
* Stephen Leake fgrcura_yr...@fgrcur-yrnxr.bet [2012-07-08 03:49:02 -0400]: Sam Steingold s...@gnu.org writes: Can you explain why you want to override your choice for bbdb-message-all-addresses in this function? when I try to edit a field when bbdb-message-all-addresses is t, the record being edited is the first record displayed, not the record of the sender. I gather you think that's wrong, even though it is what you requested. Apparently you want to set bbdb-message-all-addresses to nil, not t. Why did you set it to t? It defaults to nil, so you set it deliberately. I want all the relevant records for a message displayed, but when I hit ;, I want to edit the record of the sender, not the first record displayed. -- Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000 http://www.childpsy.net/ http://openvotingconsortium.org http://dhimmi.com http://thereligionofpeace.com http://think-israel.org Feynman: 'Philosophy of science is as useful to scientists as ornithology is to birds' -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
nameless records
When I receive a confirmation message from no-re...@foo.com, I create a record and copy into its notes the url and all the relevant information about the service I just registered for. Since bbdb creates a record with first name no-reply and last name , loading the file becomes very slow because bbdb pauses for a second to report that I have a dozen duplicates for webmaster, no-reply, bugzilla-daemon c c. I don't think it makes much sense to add first name/last name to such records. It seems that treating the e-mail names just like AKAs is better. I.e., right now a record is assumed to already have name X if X matches either bbdb-record-name or one of bbdb-record-aka. Proposal: additionally, assume a record to already have name X if X matches one of (defun address-name (address) (if (string-match @ address) (substring address 0 (match-beginning 0)) address)) (mapcar #'address-name (bbdb-record-mail record)) Thanks. -- Sam Steingold (http://sds.podval.org/) on Ubuntu 12.04 (precise) X 11.0.11103000 http://www.childpsy.net/ http://camera.org http://openvotingconsortium.org http://iris.org.il http://www.memritv.org http://pmw.org.il C combines the power of assembler with the portability of assembler. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: [BBDB] ChangeLog 2012-07-06
Sam Steingold s...@gnu.org writes: (snip discussing bbdb-message-all-addresses) I want all the relevant records for a message displayed, I guess when bbdb pops up automatically for a message. but when I hit ;, I want to edit the record of the sender, not the first record displayed. Ok, that makes sense. ; is bound to 'bbdb-mua-edit-field-sender, so it does seem to be doing the wrong thing, by editing a record that is not the sender. However, when I hit ;, it does edit the sender, not the first record in the list. So apparently my code is different from yours. Similarly, when I hit : (bbdb-gnus-display-sender), it shows the correct record. I'm not familiar with git; how do I identify what revision of bbdb source I'm currently using? -- -- Stephe -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/
Re: [BBDB] ChangeLog 2012-07-08
On Sun Jul 8 2012 Roland Winkler wrote: 2012-07-08 Roland Winkler wink...@gnu.org * lisp/bbdb-mua.el (bbdb-update-records): Make records a list ordered like address-list. 2012-07-08 Roland Winkler wink...@gnu.org * lisp/bbdb-mua.el (bbdb-update-records): Fix previous patch. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ bbdb-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bbdb-info BBDB Home Page: http://bbdb.sourceforge.net/