Bastien wrote: > Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > >> As a side note, "forbidding" blank lines between headlines and the >> properties drawer (or better just after the planning line, if any) would >> make parsing easier and faster in a lot of cases. Unfortunately, I think >> this would break a lot of files, too. > > Well, we can poll users and see how inconvenient this change would be. > > (I'm certainly biased here, as I never use blank lines between the > headline and the properties drawer.) > > If it's not too inconvenient, we can plan this for Org 9.0.
Sorry for taking too much time to answer, but I'm under constant flood here, because of holiday times and the such. First, please note I wouldn't flag the bug as being caused by a property drawer detached from the headline. For me, the problem (in the ECM I gave) is interpreting the contents of the Org code block (in the given case: an headline with a property drawer following it). I regard that "interpretation" of what's inside the Org code block as the real cause of the problem. Maybe interpretation is not the right term, but the code block should never be allowed to be scanned when searching properties of the current headline IMHO. Second, I neither never ever have property drawers separated from headlines. I think that could be safely enforce, anyway, as all the tools in Org (C-c C-x p, C-c C-x C-i, C-c C-s, C-c C-d, etc.) never make such a case appear. Best regards, Seb -- Sebastien Vauban
