Unfortunately, the macro was moved from peg.el to peg-tests.el in
later versions of peg, so we copy it for our use here.
Fixes#75. Thanks to Karl Voit (@novoid) and @karlicoss for
reporting.
Released as 0.4.6.
Using a different major mode in org-ql-view buffers causes some Org Agenda
remote commands to not work, because they test whether the major mode
is org-agenda-mode. Even though these remote commands are not
guaranteed to work, it was not intended to break them now, so this
restores compatibility with them.
Fixes#102. Thanks to Alois Janíček (@aloisjanicek) for reporting.
This reverts commit ba7d4a2e82.
Released as 0.4.4.
Use a derived major mode for org-ql-view buffers, and ensure that mode
is active when calling org-ql-view-refresh, to avoid interfering with
buffers in other modes if the user calls the command by accident.
See
<b87156f2bb>.
Thanks to Alois Janíček (@AloisJanicek) for discovering the bug.
Released as 0.4.3.
Even when org-done-keywords-for-agenda is nil. I'm not sure when this
was broken, but the logic was wrong in this function, and this is the
intended behavior, so this is a bug fix.
Released as 0.4.2.
These predicates are analogs to the existing "children" and
"descendents" predicates.
They may be useful for testing parents for specific todo states, or if
they have non-inherited tags (i.e. tags from
"org-tags-exclude-from-inheritance").
Closes#71. Thanks to @xeijin.
Squashed commit of the following:
commit edac9c6960
Author: Adam Porter <adam@alphapapa.net>
Date: Sat Jan 18 20:24:28 2020 -0600
Adjust message, indentation, add changelog entry
commit 6a263e34ff
Author: xeijin <xeijin@users.noreply.github.com>
Date: Fri Jan 3 19:08:10 2020 +0000
removing view title
commit fc37e3f146
Author: xeijin <xeijin@users.noreply.github.com>
Date: Mon Dec 9 22:47:00 2019 +0000
confirmation message for org-ql-view-refresh
In keeping with the message displayed by `g` when refreshing an
org-agenda buffer - if nothing has changed in an `org-ql` buffer
it can sometimes be difficult to determine if the refresh took
place at all.
Emacs 27 marks map-put as obsolete and renames it to map-put!, which
causes byte-compilation warnings (sigh...isn't that the definition of
useless churn?). Of course, map-put! doesn't exist in Emacs 26, so we
can't just use that. I'm beginning to think that it will never be
possible to make the linting clean.
It's more valuable to see at a glance that the tests passed than to
have every run indicate failure because of lint failures, especially
when some of the lint failures come from package-lint issues that may
be patched in the future.
