From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Leech-Pepin Subject: Re: bug in org-habits Date: Tue, 03 Nov 2015 16:48:03 -0500 Message-ID: <315DDEDC-1BD9-4680-A8C8-B36821EB931C@gmail.com> References: <871tc83p01.fsf@flynn.nichework.com> <84io5j1k5h.fsf@gmail.com> <84611j19hk.fsf@gmail.com> <5638C2A1.2090801@iancu.ch> <87h9l32gfc.fsf@nicolasgoaziou.fr> <87d1vq3mh4.fsf@nicolasgoaziou.fr> <874mh23iw0.fsf@nicolasgoaziou.fr> <878u6eu5wg.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43725) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZtjR8-0002bF-AH for emacs-orgmode@gnu.org; Tue, 03 Nov 2015 16:48:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZtjR3-0004FI-Ak for emacs-orgmode@gnu.org; Tue, 03 Nov 2015 16:48:14 -0500 Received: from mail-yk0-x233.google.com ([2607:f8b0:4002:c07::233]:35314) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZtjR3-0004Eu-5j for emacs-orgmode@gnu.org; Tue, 03 Nov 2015 16:48:09 -0500 Received: by ykek133 with SMTP id k133so40136642yke.2 for ; Tue, 03 Nov 2015 13:48:08 -0800 (PST) In-Reply-To: <878u6eu5wg.fsf@Rainer.invalid> 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: Achim Gratz , emacs-orgmode@gnu.org On November 3, 2015 4:31:11 PM EST, Achim Gratz wrote: >John Wiegley writes: >> Thanks for discussing this with me, Nicolas. I appreciate there may >be >> technical complexities involved. Could we special-case allow >PROPERTIES to be >> the *very last thing* in an entry? I don't need it to float anywhere >else. I >> just like it to be at the end. > >Well, that's precisely the thing that doesn't scale and that Nicolas >wanted to avoid. Putting the properties at the beginning of an entry >makes the search pretty much constant time and if you find something >else at the start of the entry then you know there aren't any and can >go >on (this is pretty important for making sure property inheritance works >correctly, among other things). If you could put them _anywhere_ else, >you'd have to keep searching until you either find them or you've >exhausted the span of the entry. Wouldn't last item in entry scale without issues? Find end of headline (start of next or end of buffer) and search backwards. If first element from end is a property drawer you have it, otherwise you still know there is none. Jon > >Regards, >Achim. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.