Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> I would have liked to know what the "something else" was! Or even "Org
>> link regexps have been rewritten", something like that.
>
> I added an obsolescence warning about it in "org-compat.el". It will
> still break upstream, sin
Hello,
Eric Abrahamsen writes:
> I would have liked to know what the "something else" was! Or even "Org
> link regexps have been rewritten", something like that.
I added an obsolescence warning about it in "org-compat.el". It will
still break upstream, since there is no replacement for the vari
On 03/11/20 23:20 PM, Nicolas Goaziou wrote:
> Hello,
>
> Eric Abrahamsen writes:
>
>> But if we use `make-obsolete-variable', the CURRENT-NAME arg can be a
>> simply explanatory string.
>
> You're right. However, I'm not sure what the CURRENT-NAME should be,
> besides "don't use this, you proba
Hello,
Eric Abrahamsen writes:
> But if we use `make-obsolete-variable', the CURRENT-NAME arg can be a
> simply explanatory string.
You're right. However, I'm not sure what the CURRENT-NAME should be,
besides "don't use this, you probably want something else"
Also, my suggestions still holds:
Nicolas Goaziou writes:
> Hello,
>
> Julien Cubizolles writes:
>
>> I'm using org-caldav (https://github.com/dengste/org-caldav/) to
>> synchronize the calendar on my Android phone and Org. Recently this
>> synchronization stopped working because org-caldav relies on
>> org-maybe-keyword-time-re
Hello,
Julien Cubizolles writes:
> I'm using org-caldav (https://github.com/dengste/org-caldav/) to
> synchronize the calendar on my Android phone and Org. Recently this
> synchronization stopped working because org-caldav relies on
> org-maybe-keyword-time-regexp that has been dropped from Org.
