From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Tangling takes long - profiling and calling R Date: Fri, 03 Jul 2015 15:43:58 +0200 Message-ID: <87fv56uv8i.fsf@nicolasgoaziou.fr> References: <87ioaobvl1.fsf@selenimh.access.network> <87a8vzc1u8.fsf@selenimh.access.network> <07F390A6-B112-4E02-8417-E9280B24AC94@gmail.com> <87zj3gj7qg.fsf@gmail.com> <87h9pmn5fh.fsf@nicolasgoaziou.fr> <878uaybktx.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41311) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZB1Eg-0005IY-3u for emacs-orgmode@gnu.org; Fri, 03 Jul 2015 09:42:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZB1Ee-0005Uh-Rc for emacs-orgmode@gnu.org; Fri, 03 Jul 2015 09:42:34 -0400 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:55991) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZB1Ee-0005UX-KT for emacs-orgmode@gnu.org; Fri, 03 Jul 2015 09:42:32 -0400 In-Reply-To: <878uaybktx.fsf@gmail.com> (Aaron Ecay's message of "Thu, 02 Jul 2015 17:11:54 +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.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Rainer M Krug Cc: Sebastien Vauban , "emacs-orgmode@gnu.org" Aaron Ecay writes: > Could you take a look at > , specifically the > paragraph beginning =E2=80=9CThat looks like a bug=E2=80=9D? This should be fixed in 188bae903feb942355dae6878951e9f13211e1d0. Thank you for the notice. > I don=E2=80=99t want to argue the semantics excessively, but =E2=80=9Cdep= recated=E2=80=9D should > mean that users: > 1) actually change their behavior when creating new documents, or at > least > 2) are aware that the old behavior is in danger of disappearing. > > A footnote in the manual and a comment in the elisp file don=E2=80=99t re= ally > achieve this, as evidenced by the periodic discussions of this point that > we have. This is why I suggest to also announce the deprecation in ORG-NEWS, then effectively remove it in the next release. > Additionally, last year Eric commented that the deprecation was > =E2=80=9Cpremature=E2=80=9D . This > arguably means (among other things) that more effort to publicize it and > work on its replacement is needed, something that has not really > happened. Let's move forward and discuss about what is needed then. > Neither syntax is necessary, by this metric. We could just make do with > local arguments, not needing properties at all. > > IOW, this doesn=E2=80=99t distinguish between these two approaches. You may be misunderstanding me. I don't want to distinguish between these approaches. Both are certainly fine, but two of them in one too many. This is just confusing and more difficult to maintain. >> I suggest to remove the old "dynamic" setting and improve the new >> "lexical" one, if needed.=20 > > The dynamic vs. lexical metaphor is not very helpful either. It doesn't matter. Let's call one the "old" setting and the other the "recent" setting. Or tag them "A" and "B". > There has been no justification for the new property system proposed > other than questions of taste such as the above, and efficiency. The > efficiency considerations could be solved in several ways. One obvious > one would be to use a single call to org-entry-properties rather than N > calls to org-entry-get. I feel like a broken record saying this, but it > was a solution I suggested already, in the last thread > . Another, more > ambitious, solution would be to use the parser cache for > org-entry-{properties,get}. There was a patch for this > , which never landed > for a variety of reasons. I don't think efficiency is a matter here. `org-entry-get' is reasonably fast nowadays (since properties drawers change), even using inheritance. Regards,