From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: removal of org-maybe-keyword-time-regexp Date: Wed, 11 Mar 2020 14:29:42 -0700 Message-ID: <87pndi4m2h.fsf@ericabrahamsen.net> References: <871rpyerjw.fsf@free.fr> <87k13qoaxx.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:52522) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jC8vJ-0005aT-7T for emacs-orgmode@gnu.org; Wed, 11 Mar 2020 17:29:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jC8vI-0007Sq-08 for emacs-orgmode@gnu.org; Wed, 11 Mar 2020 17:29:53 -0400 Received: from ciao.gmane.io ([159.69.161.202]:53902) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jC8vH-0007Qc-Qa for emacs-orgmode@gnu.org; Wed, 11 Mar 2020 17:29:51 -0400 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1jC8vE-000CgV-63 for emacs-orgmode@gnu.org; Wed, 11 Mar 2020 22:29:48 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org 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-regexp that has been dropped from Org. As a >> workaround, could this variable be reintroduced in org so as not to >> break this very useful packageĀ ? > > Could you contact upstream instead? > > AFAICT, they use this variable only twice. The first occurrence doesn't > seem useful (they check for a planning info keyword in a headline, which > cannot happen), it is probably enough to look for `org-ts-regexp-both'. > > I'm not sure about the second one. I guess it would be better for them > to use something like: > > (and (re-search-forward "org-planning-line-re" nil t) > (org-at-planning-p) > (progn > (org-skip-whitespace) > (looking-at org-ts-regexp-both))) > > The (small) issue here is that we cannot properly deprecate a variable > that is not replaced with something else (i.e., we're not using > `define-obsolete-variable-alias' here). But if we use `make-obsolete-variable', the CURRENT-NAME arg can be a simply explanatory string. I was also recently bit by the removal of a bunch of regexps (in my case, link regexps), and it would have been useful to have some sort of a pointer, either in the obsolescence message or in the docs, about what we're supposed to do instead.