Re: %%(org-bbdb-anniversaries)

2014-06-25 Thread Glyn Millington
Steven Arntson ste...@stevenarntson.com writes:

 Glyn Millington glyn.milling...@gmail.com writes:

 Steven Arntson ste...@stevenarntson.com writes:

 My previous issues with BBDB suddenly not working are resolved, thanks
 to this list! And I'm now persevering into the world of linking my BBDB
 anniversaries fields with my org-agenda.

 I've got a diary.org file set up, which I added to my agenda files. I
 added the following lines to diary.org:

 * Anniversaries
 #+CATEGORY: Anniv
 %%(org-bbdb-anniversaries)

 However, when I try to bring up my org-agenda now (M-x org-agenda
 a), the message I receive is:

 Bad sexp at line 13 in /home/steven/diary.org: (org-bbdb-anniversaries)

 Line #13 is the final line in the excerpt above. Does anyone know why
 I'm getting this error?

 Ok - here's an even wilder guess than last time!

 I read this in org-bbdb.el

 ,
 | ;; It also implements an interface (based on Ivar Rummelhoff's
 | ;; bbdb-anniv.el) for those org-mode users, who do not use the diary
 | ;; but who do want to include the anniversaries stored in the BBDB
 | ;; into the org-agenda.  If you already include the `diary' into the
 | ;; agenda, you might want to prefer to include the anniversaries in
 | ;; the diary using bbdb-anniv.el.
 `

 ie there are two possible ways of doing this depending on whether you
 use the emacs
 diary/calendar system or not.

 And I noticed that in the slice of your config you posted in your last
 query that you have a call to bbdb-anniv. 

 And I wonder if the two ways clash if you use 'em together! Haven't got
 time or talent to probe this properly. 

 You could try commenting out the bbdb-anniv stuff and see that works.

 You could try commenting out  %%(org-bbdb-anniversaries) and see if that
 works.  I'm betting it will :-)

 atb

 Glyn


 
 Glyn,

 You are batting 1000! That was exactly the problem. I commented out the
 line from my diary.org file, and it now works perfectly.


Splendid!


 It's an odd thing about emacs that I search around and encounter
 different ideas, which I cobble together. Sometimes my still-developing
 emacs literacy level is insufficient to perceive that I'm combining
 different approaches. Part of me wishes the process were more
 straightforward, but I've also learned a lot by futzing around that I
 wouldn't have otherwise. I think it's a net gain.

As a fellow futzer I can only agree!  

atb




Glyn


--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Re: %%(org-bbdb-anniversaries)

2014-06-24 Thread Eric Abrahamsen
Steven Arntson ste...@stevenarntson.com writes:

 My previous issues with BBDB suddenly not working are resolved, thanks
 to this list! And I'm now persevering into the world of linking my BBDB
 anniversaries fields with my org-agenda.

 I've got a diary.org file set up, which I added to my agenda files. I
 added the following lines to diary.org:

 * Anniversaries

 #+CATEGORY: Anniv
 %%(org-bbdb-anniversaries)

 However, when I try to bring up my org-agenda now (M-x org-agenda a), the 
 message I receive is:

 Bad sexp at line 13 in /home/steven/diary.org: (org-bbdb-anniversaries)

 Line #13 is the final line in the excerpt above. Does anyone know why
 I'm getting this error?

 Thank you!
 Steven Arntson

There might be more than one way to address this, but what I do is give
my BBDB contacts an anniversary field, like:

anniversary: 1948-03-08 birthday

Then in my Org setup:

(setq org-agenda-include-diary t)

And in my BBDB setup:

(require 'bbdb-anniv)
(add-hook 'diary-list-entries-hook 'bbdb-anniv-diary-entries)

Am I missing anything? I think that's all the relevant stuff. I like
this because the anniversaries are on the contacts themselves, where (I
feel) they belong, and I don't need a diary.org file. They just show up
in the agenda where they're supposed to.

Hope that works!
Eric


--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Re: %%(org-bbdb-anniversaries)

2014-06-24 Thread Glyn Millington
Steven Arntson ste...@stevenarntson.com writes:

 My previous issues with BBDB suddenly not working are resolved, thanks
 to this list! And I'm now persevering into the world of linking my BBDB
 anniversaries fields with my org-agenda.

 I've got a diary.org file set up, which I added to my agenda files. I
 added the following lines to diary.org:

 * Anniversaries
 #+CATEGORY: Anniv
 %%(org-bbdb-anniversaries)

 However, when I try to bring up my org-agenda now (M-x org-agenda a), the 
 message I receive is:

 Bad sexp at line 13 in /home/steven/diary.org: (org-bbdb-anniversaries)

 Line #13 is the final line in the excerpt above. Does anyone know why
 I'm getting this error?

Ok - here's an even wilder guess than last time!

I read this in org-bbdb.el

,
| ;; It also implements an interface (based on Ivar Rummelhoff's
| ;; bbdb-anniv.el) for those org-mode users, who do not use the diary
| ;; but who do want to include the anniversaries stored in the BBDB
| ;; into the org-agenda.  If you already include the `diary' into the
| ;; agenda, you might want to prefer to include the anniversaries in
| ;; the diary using bbdb-anniv.el.
`

ie there are two possible ways of doing this depending on whether you use the 
emacs
diary/calendar system or not.

And I noticed that in the slice of your config you posted in your last
query that you have a call to bbdb-anniv. 

And I wonder if the two ways clash if you use 'em together! Haven't got
time or talent to probe this properly. 

You could try commenting out the bbdb-anniv stuff and see that works.

You could try commenting out  %%(org-bbdb-anniversaries) and see if that
works.  I'm betting it will :-)

atb

Glyn


--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Re: org-bbdb-anniversaries gives error 'bad sexp'

2011-05-16 Thread Matt Lundin
Roland Winkler wink...@gnu.org writes:

 On Sun May 15 2011 Matt Lundin wrote:
 I'd be happy to take this on. AFAICT, there are three functions in
 org-bbdb that no longer exist in bbdb v3.
 
 bbdb-name
 bbdb-company
 bbdb-record-getprop
 
 The first two can easily be defaliased to bbdb-search-organization and
 bbdb-search-name. (For a while, we should probably support bbdb v2 and
 v3 simultaneously.)

 Things might be a bit more subtle. The new organization field is
 a list, not a single string.

Thanks. That's good to know. AFAICT, bbdb-search-organization already
accommodates for this fact. That is, if you give it a regexp, it will
return all records matching the regexp in the organization field. Since
org-bbdb calls bbdb-company with a string as an argument, wouldn't a
defalias be sufficient for the time being?

 The other major change that breaks compatibility is the order of the
 parameters in bbdb-split. It has been reversed in the new bbdb: i.e.,
 one used to call (bbdb-split string separator), whereas now one must
 call (bbdb-split separator string). Is there a compelling reason to
 change this order in the new bbdb?

 The change is not only with respect to the order of arguments that
 could be reverted in BBDB v3. More importantly, I tried to get rid
 of hard-coded separators. Most often the separator arg is now the
 name of the field that is split. Then the actual separator is looked
 up in bbdb-separator-alist. While I do not know yet a good strategy
 for the upgrade of org-mode's BBDB interface, I'd find it
 unfortunate if such a feature was lost in org-mode to preserve
 backward compatibility.

Thanks for the explanation. For the time being, I'll add a workaround to
accommodate both versions.

Best,
Matt

--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Re: org-bbdb-anniversaries gives error 'bad sexp'

2011-05-16 Thread Matt Lundin
Leo sdl@gmail.com writes:

 On 2011-05-16 00:58 +0800, Matt Lundin wrote:
 I'd be happy to take this on. AFAICT, there are three functions in
 org-bbdb that no longer exist in bbdb v3.

 If you want you can build on top of my version. The anniversaries is
 still broken since I don't use BBDB-anniv.el. The rest works well for
 the past few weeks.

Thanks Leo! This is very helpful.

I have anniversaries working in my own setup, so between the two sets of
modifications, I should be able to provide a full set of fixes. More
soon...

Best,
Matt

--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Re: org-bbdb-anniversaries gives error 'bad sexp'

2011-05-15 Thread Roland Winkler
On Sat May 14 2011 Johnny wrote:
 I have set up an org-agenda that includes anniversaries in the agenda
 view from the bbdb database, but this breaks with bbdb 3.02 giving the
 error 'bad sexp'. 
 
 I set up the agenda file using (from org-mode 6.33x info section 10.3.1):
 
 * Anniversaries
 :PROPERTIES:
 :CATEGORY: Anniv
 :END
 %%(org-bbdb-anniversaries)
 
 Any ideas?

I need to say that I do not know how org-mode interfaces with BBDB.
I am CC'ing this email also to emacs-orgm...@gnu.org.

If org-mode is set up to work with BBDB v2.x, (most likely) this
does not work with BBDB v3. Defining aliases for the old BBDB
functions in terms of the new ones would work only in a few cases.
Of course, this depends first of all on how org-mode is supposed to
work with BBDB.

Yet we are trying to make the new BBDB part of GNU Emacs. So it
would be great if org-mode could be updated to provide (also) an
interface for the new BBDB.

While I'd like to declare soon that BBDB v3 has reached a beta
stage, it was probably good if someone familiar with org-mode's
interface to BBDB could take a look into this so that we could try
to make sure that the new BBDB can work with org-mode as smoothly as
possible. (Various add-ons for BBDB v2 had to go through some pain
to work as intended by advicing BBDB functions and things like that.
With BBDB v3 I tried to clean up and simplify these things; and
various add-ons for BBDB v2 are already incorporated into v3 in one
or the other way. It would probably be good if the needs of org-mode
could be incorporated into the new BBDB before we declare that BBDB
v3 has reached a beta stage.)

Roland

--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Re: org-bbdb-anniversaries gives error 'bad sexp'

2011-05-15 Thread Roland Winkler
On Sun May 15 2011 Roland Winkler wrote:
 It would probably be good if the needs of org-mode could be
 incorporated into the new BBDB before we declare that BBDB v3 has
 reached a beta stage.)

I forgot to say:

It is an item on the todo list for BBDB v3 to provide a more complete
list for how things have changed from BBDB v2 to v3.

Roland

--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/


Re: org-bbdb-anniversaries gives error 'bad sexp'

2011-05-15 Thread Roland Winkler
On Sun May 15 2011 Matt Lundin wrote:
 I'd be happy to take this on. AFAICT, there are three functions in
 org-bbdb that no longer exist in bbdb v3.
 
 bbdb-name
 bbdb-company
 bbdb-record-getprop
 
 The first two can easily be defaliased to bbdb-search-organization and
 bbdb-search-name. (For a while, we should probably support bbdb v2 and
 v3 simultaneously.)

Things might be a bit more subtle. The new organization field is
a list, not a single string.

 What is the new name of bbdb-record-getprop (the function that
 retrieves the value of a given label in a record)? My best guess
 is bbdb-record-note, but I want to confirm this.

That's mostly true. bbdb-record-getprop also retrieved the company field.

 The other major change that breaks compatibility is the order of the
 parameters in bbdb-split. It has been reversed in the new bbdb: i.e.,
 one used to call (bbdb-split string separator), whereas now one must
 call (bbdb-split separator string). Is there a compelling reason to
 change this order in the new bbdb?

The change is not only with respect to the order of arguments that
could be reverted in BBDB v3. More importantly, I tried to get rid
of hard-coded separators. Most often the separator arg is now the
name of the field that is split. Then the actual separator is looked
up in bbdb-separator-alist. While I do not know yet a good strategy
for the upgrade of org-mode's BBDB interface, I'd find it
unfortunate if such a feature was lost in org-mode to preserve
backward compatibility.

Roland

--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/