Fix: Planning-related predicates searched too far into entries

Planning-line-related predicates searched entire entries, which could
find lines that looked like planning lines but were not.  For example, in an
entry talking about tiny.el, in a source code block, in Elisp comments
that had text resembling an Org planning line, that text would be
found by the regexp search, and the predicate would then attempt to
parse the match, which could fail.

Now the regexp search for planning-line-related predicates is bound by
the end of the line after the heading, which is the only place that
actual Org planning lines are supposed to be.
This commit is contained in:
Adam Porter 2019-08-30 05:23:39 -05:00
parent d8d2455a2c
commit e839397579
2 changed files with 25 additions and 13 deletions

View file

@ -476,6 +476,7 @@ Expands into a call to ~org-ql-select~ with the same arguments. For convenience
+ Don't search buffers without headings, and show a message if the user attempts it.
+ Don't search hidden/special buffers.
+ Properly accept arbitrary sort functions in =org-ql-select=, etc. (Fixes [[https://github.com/alphapapa/org-ql/issues/37][#37]]. Thanks to [[https://github.com/mz-pdm][Milan Zamazal]].)
+ Planning-line-related predicates searched too far into entries.
*Compatibility*
+ Fixes for compatibility with Org 9.2. (Thanks to [[https://github.com/ataias][Ataias Pereira Reis]] and [[https://github.com/dakra][Daniel Kraus]].)