Re: org-bbdb-anniversaries, bbdb v3

Re: org-bbdb-anniversaries, bbdb v3

[Marco Wahl]

Hi,

> should I expect org-bbdb-anniversaries to work with bbdb v3? There was a
> bit of discussion a couple of years ago and in org-bbdb.el are some
> references to bbdb v3.

Currently I happily use (bbdb-version)"BBDB version 3.1.2" to store
anniversaries which appear in my agenda with (org-version)"8.3.3".

BTW I use `org-bbdb-anniversaries-future'.  See section "Anniversaries
from BBDB" in the info documentation (info "(org) Weekly/daily agenda").


Best regards,
-- 
Marco Wahl
GPG: 0x49010A040A3AE6F2

Re: org-bbdb-anniversaries, bbdb v3

[Nick Dokos]

Michael Welle <mwe012008@gmx.net> writes:

> Hello,
>
> Marco Wahl <marcowahlsoft@gmail.com> writes:
>
>> Hi,
>>
>>> should I expect org-bbdb-anniversaries to work with bbdb v3? There was a
>>> bit of discussion a couple of years ago and in org-bbdb.el are some
>>> references to bbdb v3.
>>
>> Currently I happily use (bbdb-version)"BBDB version 3.1.2" to store
>> anniversaries which appear in my agenda with (org-version)"8.3.3".
>>
>> BTW I use `org-bbdb-anniversaries-future'.  See section "Anniversaries
>> from BBDB" in the info documentation (info "(org) Weekly/daily agenda").

> I use Org 8.3.4 from the repository. There is no o-b-a-f in it, just the
> regular org-bbdb-anniversaries.

That's strange: I just updated to 8.3.4 and o-b-a-f is present.

> Do you have attributes like 'birthday:
> 1900-1-1' or like 'anniversary: 1900-1-1 birthday' in your bbdb?
>

The latter:

        anniversary: 1900-01-01 birthday
                     1901-01-11 wedding

-- 
Nick

Re: org-bbdb-anniversaries-future

[Georges]

Nick Dokos <ndokos <at> gmail.com> writes:

> Michael Welle <mwe012008 <at> gmx.net> writes:
> 
> > Marco Wahl <marcowahlsoft <at> gmail.com> writes:
> >
> >> BTW I use `org-bbdb-anniversaries-future'.  See section "Anniversaries
> >> from BBDB" in the info documentation (info "(org) Weekly/daily agenda").


Not present in latest org elpa package.

--

Re: org-bbdb-anniversaries, bbdb v3

[Nick Dokos]

Michael Welle <mwe012008@gmx.net> writes:

>>> I use Org 8.3.4 from the repository. There is no o-b-a-f in it, just the
>>> regular org-bbdb-anniversaries.
>>
>> That's strange: I just updated to 8.3.4 and o-b-a-f is present.
> indeed:
>
> ~/.emacs.d/elpa/org-plus-contrib-20160307> grep -ri org-bbdb-anniversaries-future *
> ~/.emacs.d/elpa/org-plus-contrib-20160307> 
>
> Is that a function in org-bbdb.el?
>

Yes:

,----
| org-bbdb-anniversaries-future is an autoloaded compiled Lisp function
| in ‘../org-mode/lisp/org-bbdb.el’.
| 
| (org-bbdb-anniversaries-future &optional N)
| 
| Return list of anniversaries for today and the next n-1 days (default n=7).
`----

I don't use ELPA so I may be completely wrong, but I thought ELPA
packages the maint branch, not the master branch. I think o-b-a-f
only exists in master, so it will appear in org-9.x

--
Nick

Re: org-bbdb-anniversaries, bbdb v3

[Nick Dokos]

Michael Welle <mwe012008@gmx.net> writes:

> Hello,
>
> Nick Dokos <ndokos@gmail.com> writes:
>
>> Michael Welle <mwe012008@gmx.net> writes:
>>
>>>>> I use Org 8.3.4 from the repository. There is no o-b-a-f in it, just the
>>>>> regular org-bbdb-anniversaries.
>>>>
>>>> That's strange: I just updated to 8.3.4 and o-b-a-f is present.
>>> indeed:
>>>
>>> ~/.emacs.d/elpa/org-plus-contrib-20160307> grep -ri
>>> org-bbdb-anniversaries-future *
>>> ~/.emacs.d/elpa/org-plus-contrib-20160307> 
>>>
>>> Is that a function in org-bbdb.el?
>>>
>>
>> Yes:
>>
>> ,----
>> | org-bbdb-anniversaries-future is an autoloaded compiled Lisp function
>> | in ‘../org-mode/lisp/org-bbdb.el’.
>> | 
>> | (org-bbdb-anniversaries-future &optional N)
>> | 
>> | Return list of anniversaries for today and the next n-1 days (default n=7).
>> `----
>>
>> I don't use ELPA so I may be completely wrong, but I thought ELPA
>> packages the maint branch, not the master branch. I think o-b-a-f
>> only exists in master, so it will appear in org-9.x
> ah, that was my question in my other post. I found your change set in
> master, but wasn't unsure on which branch the packages are based.
>
> Now I have to make my mind up, if I just wait or if I pull the master
> branch ;). 
>

I don't think o-b-a-f by itself is sufficient reason to upgrade :-)

I'm not going to say anything new or profound here, but it's worth
reiterating:

- if you depend on current org for "production" (with deadlines and
  deliverables that cannot be compromised), then you should probably
  leave your work machine alone. If you want to test, you should probably
  install master on a different machine (if you don't have a different
  physical machine, a VM will do fine) and test carefully before
  upgrading your work machine.

- if you can afford some breakage in your workflows and can either debug
  the failures or provide detailed information (backtraces, profiles
  etc) about them, I think the devs would appreciate that, but any
  testing you can do is probably worthwhile.

- That said, I think master is very stable, but there are backward
  incompatibilities in various places (check ORG-NEWS for details
  and the mailing list for breakage reports to see if they would affect
  you). The sooner you start getting ready, the smoother the transition
  will be.

--
Nick

Re: org-bbdb-anniversaries, bbdb v3

[Nick Dokos]

Michael Welle <mwe012008@gmx.net> writes:

> Hello,
>
> I got org-bbdb from the master branch (and all the other files from the
> package), wrote a small function that can parse the date format of my
> bbdb and now it works as expected. 
>

I don't want to discourage you from such experimentation, but I think
this is something to be avoided in general: you have a frankenstein
installation that cannot be easily up- or down-graded to fix problems
and any problems you encounter will have to be passed through a filter
to figure out whether they arise from your specific installation method
or whether they apply to org in general. IOW, it is less useful both to
you (except for getting o-b-a-f, I guess) and to the developers than
either straight maint or straight master.

--
Nick