On November 3, 2015 4:31:11 PM EST, Achim Gratz <strom...@nexgo.de> 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.
