Hi Samuel,
Thanks for your note. Just FYI, the earlier parser code in this thread
has
been superseded by the code in the post "new tag query parser [3/5]".
The sexp input is a nice idea, and it would be very easy I think.
The function org-make-tags-matcher now takes a query string
but could
You have really dived into this. I think it's excellent to allow more
flexibility in searches.
Just a brainstorm question, but having just modified the code, how
difficult do you think it would be to provide a sexp syntax?
Despite all of your obvious hard work, I'd find sexp easier to look
up, m
A small addendum:
Right after I posted (of course!), I noticed both a small mistake and an
opportunity for
simplification, relating to detecting and processing the todo expressions
after a /.
Specifically, the approximate fix I proposed to the bug in the 7.8 code is
insufficient
to handle regexp m
