Adam Porter

The issue is that tokens passed to the `rifle`/`smart` predicate are anchored to the beginning of a word: https://github.com/alphapapa/org-ql/blob/eb5377320fcfd38354d6e9e3e655969ae3c0e052/org-ql.el#L1642 So they can match parts of a word, but only at...

Hi Ahmed, Well, first let me nitpick about jargon: in Org terms, an "entry" is a heading and the contents of its body, not including any child entries. If we...

Well, being software, anything is possible. But org-ql's core procedures are designed around searching entries. As for the `org-ql-view` library, well, it just displays a list of results, which begin...

Well, I'm generally glad to help, but I'm not sure what I can add here. It seems like trying to integrate the two would require a lot of hacky changes,...

You're welcome.

I don't know. It depends on how invasive the changes would be and how they might affect performance. I expect it would require conditionals in many places, which I would...

Sorry, but I will have to ask you to disentangle this and #348, as they both contain some of the same changes. Magit should make it easy enough; I'd suggest...

It's always easiest to deal with a commit near the tip of the branch it's to be merged into, so rebasing is preferred. Sometimes I do the rebasing myself if...

Hello Bob, Well, there appear to be a few different issues at play here. 1. When you call `org-ql-sparse-tree`, you're using non-sexp queries, equivalent to `(and (property "TESTED") "y")` and...

@AndrewGabelliTR Those sexp and string queries are equivalent. If a case were found in which they were not 1:1 compatible, it would be a bug. If you want to ignore...