234 lines
12 KiB
Org Mode
234 lines
12 KiB
Org Mode
#+TITLE: org-ql
|
|
|
|
~org-ql~ is a lispy query language for Org files. It allows you to find Org entries matching certain criteria and perform actions on them, such as collecting their parsed representation with ~org-element~ (the default action).
|
|
|
|
* Examples
|
|
|
|
More examples are available in [[examples.org]].
|
|
|
|
#+BEGIN_SRC elisp
|
|
;; Return a list of Org entry elements in the file "~/org/main.org" which have the SOMEDAY
|
|
;; to-do keyword, are tagged "Emacs", and have priority B or higher.
|
|
(org-ql "~/org/main.org"
|
|
(and (todo "SOMEDAY")
|
|
(tags "Emacs")
|
|
(priority >= "B"))) ;=> ((headline (:raw-value "org-board" :begin 1220270 :end 1220403 ...)) ...)
|
|
|
|
;; Return a list of bills coming due, searching all Org Agenda files, sorted by deadline. Deadlines
|
|
;; are compared with configured Org warning days, which is implied by the plain `<=' in the
|
|
;; `deadline' matcher.
|
|
(org-ql (org-agenda-files)
|
|
(and (not (done))
|
|
(tags "bills")
|
|
(deadline <=))
|
|
:sort deadline)
|
|
|
|
;; Set the tag "Emacs" on every entry in the inbox file that mentions "Emacs".
|
|
(org-ql "~/org/inbox.org"
|
|
(regexp "Emacs")
|
|
:action (org-toggle-tag "Emacs" 'on))
|
|
|
|
;; If you kept a database of music in an Org file, you might run a query like this to find tracks
|
|
;; composed by Chopin that do not have their key recorded in the database:
|
|
(org-ql "~/org/music.org"
|
|
(and (property "genre" "classical")
|
|
(property "composer" "Chopin")
|
|
(not (property "key"))))
|
|
#+END_SRC
|
|
|
|
* Usage
|
|
|
|
** Commands
|
|
|
|
*** org-ql-search
|
|
|
|
The command =org-ql-search= prompts for a query, a list of buffers or files, and how to group and sort results. Without prefix, it searches the current buffer instead of prompting. Then it presents the results in an agenda-like view.
|
|
|
|
[[images/org-ql-search.gif]]
|
|
|
|
Here's an example of using it to generate an agenda-like view for certain files in a directory tree:
|
|
|
|
[[images/org-ql-search-snippet.png]]
|
|
|
|
*** org-ql-agenda
|
|
|
|
Also included is ~org-ql-agenda~, which uses ~org-ql~ queries to select entries and present them in an Agenda-like view. It's compatible with [[https://github.com/alphapapa/org-super-agenda][org-super-agenda]], which provides grouping. For example:
|
|
|
|
#+BEGIN_SRC elisp
|
|
(org-ql-agenda "~/src/emacs/org-super-agenda/test/test.org"
|
|
(and (or (date = today)
|
|
(deadline <=)
|
|
(scheduled <= today))
|
|
(not (done)))
|
|
;; The `org-super-agenda-groups' setting is used automatically when set, or it
|
|
;; may be overriden by specifying it here:
|
|
:super-groups ((:name "Bills"
|
|
:tag "bills")
|
|
(:todo ("SOMEDAY" "TO-READ" "CHECK" "TO-WATCH" "WATCHING")
|
|
:order 7)
|
|
(:name "Personal"
|
|
:habit t
|
|
:tag "personal"
|
|
:order 3)
|
|
(:todo "WAITING"
|
|
:order 6)
|
|
(:priority "A" :order 1)
|
|
(:priority "B" :order 2)
|
|
(:priority "C" :order 2)))
|
|
#+END_SRC
|
|
|
|
Which presents this buffer:
|
|
|
|
[[images/screenshot.png]]
|
|
|
|
*Note:* The view buffer is currently put in ~org-agenda-mode~, which means that /some/ Org Agenda commands work, such as jumping to entries and changing item priorities (without necessarily updating the view). This feature is experimental and not guaranteed to work correctly with all commands. (It works to the extent it does because the appropriate text properties are placed on each item, imitating an Agenda buffer.)
|
|
|
|
Here are some other examples:
|
|
|
|
#+BEGIN_SRC elisp
|
|
;; Show an agenda-like view of items in "~/org/main.org" with TODO and SOMEDAY keywords which are
|
|
;; tagged "computer" or "Emacs" and in the category "main":
|
|
(org-ql-agenda "~/org/main.org"
|
|
(and (todo "TODO" "SOMEDAY")
|
|
(tags "computer" "Emacs")
|
|
(category "main")))
|
|
|
|
;; Show an agenda-like view of all habits in all agenda files:
|
|
(org-ql-agenda
|
|
(habit))
|
|
|
|
;; Show an agenda-like view similar to a "traditional" Org agenda.
|
|
(org-ql-agenda
|
|
(or (habit)
|
|
(date = today)
|
|
(deadline <=)
|
|
(scheduled <= today)
|
|
(and (todo "DONE" "CANCELLED")
|
|
(closed = today))))
|
|
#+END_SRC
|
|
|
|
** Functions / Macros
|
|
|
|
*** Macro: ~org-ql~
|
|
|
|
/Arguments:/ ~(buffers-or-files pred-body &key sort narrow markers action)~
|
|
|
|
Find entries in ~BUFFERS-OR-FILES~ that match ~PRED-BODY~, and return the results of running ~ACTION-FN~ on each matching entry.
|
|
|
|
~ACTION~ is a sexp which will be evaluated at each matching entry with point at the beginning of its heading. It is passed to ~org-ql--query~ as a lambda. By default, ~org-element-headline-parser~ is called to return an Org element.
|
|
|
|
~SORT~ is a user defined sorting function, or an unquoted list of one or more sorting methods, including: ~date~, ~deadline~, ~scheduled~, ~todo~, and ~priority~.
|
|
|
|
If ~NARROW~ is non-nil, query will run without widening the buffer (the default is to widen and search the entire buffer).
|
|
|
|
If ~MARKERS~ is non-nil, ~org-agenda-ng--add-markers~ is used to add markers to each item, pointing to the item in its source buffer. In this case, ~ACTION~ should return an Org element.
|
|
|
|
*** Function: ~org-ql-query~
|
|
|
|
/Arguments:/ ~(buffers-or-files query &key action narrow sort)~
|
|
|
|
Return items matching ~QUERY~ in ~BUFFERS-OR-FILES~.
|
|
|
|
~QUERY~ is an ~org-ql~ query sexp.
|
|
|
|
~ACTION~ is a function which is called on each matching entry, with point at the beginning of its heading. For example, ~org-element-headline-parser~ may be used to parse an entry into an Org element (note that it must be called with a limit argument, so a lambda must be used to do so). Also see ~org-ql--add-markers~, which may be used to add markers compatible with Org Agenda code.
|
|
|
|
If ~NARROW~ is non-nil, buffers are not widened.
|
|
|
|
~SORT~ is either nil, in which case items are not sorted; or one or a list of defined ~org-ql~ sorting methods: ~date~, ~deadline~, ~scheduled~, ~todo~, and ~priority~.
|
|
|
|
** Predicates
|
|
|
|
Arguments are listed next to predicate names, when applicable.
|
|
|
|
+ ~category (categories)~ :: Return non-nil if current heading is in one or more of ~CATEGORIES~ (a list of strings).
|
|
+ ~closed (&optional comparator target-date)~ :: Return non-nil if entry's closed date compares with ~TARGET-DATE~ using ~COMPARATOR~. ~TARGET-DATE~ should be a string parseable by ~date-to-day~. ~COMPARATOR~ should be a function (like ~<=~).
|
|
+ ~date (&optional comparator target-date)~ :: Return non-nil if Org entry at point has date of ~TYPE~ that compares with ~TARGET-DATE~ using ~COMPARATOR~. Checks all Org-formatted timestamp strings in entry. ~TYPE~ may be ~active~, ~inactive~, or ~all~, to control whether active, inactive, or all timestamps are checked. Ranges of each type are also checked. ~TARGET-DATE~ should be a string parseable by ~date-to-day~. ~COMPARATOR~ should be a function (like ~<=~).
|
|
+ ~deadline (&optional comparator target-date)~ :: Return non-nil if entry's deadline compares with ~TARGET-DATE~ using ~COMPARATOR~. ~TARGET-DATE~ should be a string parseable by ~date-to-day~. ~COMPARATOR~ should be a function (like ~<=~).
|
|
+ ~done~ :: Return non-nil if entry's ~TODO~ keyword is in ~org-done-keywords~.
|
|
+ ~habit~ :: Return non-nil if entry is a habit.
|
|
+ ~heading (regexp)~ :: Return non-nil if current entry's heading matches ~REGEXP~ (a regexp string).
|
|
+ ~level (level-or-comparator &optional level)~ :: Return non-nil if current heading's outline level matches ~LEVEL~ with ~COMPARATOR~. If ~LEVEL~ is nil, ~LEVEL-OR-COMPARATOR~ should be an integer level, which will be tested for equality to the heading's outline level. If ~LEVEL~ is non-nil, ~LEVEL-OR-COMPARATOR~ should be a comparator function (like ~<=~).
|
|
+ ~planning (&optional comparator target-date)~ :: Return non-nil if entry's planning date (deadline or scheduled) compares with ~TARGET-DATE~ using ~COMPARATOR~. ~TARGET-DATE~ should be a string parseable by ~date-to-day~. ~COMPARATOR~ should be a function (like ~<=~).
|
|
+ ~priority (&optional comparator-or-priority priority)~ :: Return non-nil if current heading has a certain priority. ~COMPARATOR-OR-PRIORITY~ should be either a comparator function, like ~<=~, or a priority string, like "A" (in which case (~=~ will be the comparator). If ~COMPARATOR-OR-PRIORITY~ is a comparator, ~PRIORITY~ should be a priority string.
|
|
+ ~property (property &optional value)~ :: Return non-nil if current entry has ~PROPERTY~ (a string), and optionally ~VALUE~ (a string).
|
|
+ ~regexp (regexp)~ :: Return non-nil if current entry matches ~REGEXP~ (a regexp string).
|
|
+ ~scheduled (&optional comparator target-date)~ :: Return non-nil if entry's scheduled date compares with ~TARGET-DATE~ using ~COMPARATOR~. ~TARGET-DATE~ should be a string parseable by ~date-to-day~. ~COMPARATOR~ should be a function (like ~<=~).
|
|
+ ~tags (tags)~ :: Return non-nil if current heading has one or more of ~TAGS~ (a list of strings).
|
|
+ ~todo (keywords)~ :: Return non-nil if current heading is a ~TODO~ item. With ~KEYWORDS~, return non-nil if its keyword is one of ~KEYWORDS~ (a list of strings).
|
|
|
|
* Notes
|
|
|
|
** Comparison with Org Agenda searches
|
|
|
|
Of course, queries like these can already be written with Org Agenda searches, but the syntax can be complex. For example, this query would be difficult to write in a standard Org Agenda search, because it matches against a to-do keyword /and/ a plain-text search. As described in the [[https://orgmode.org/worg/org-tutorials/advanced-searching.html#combining-metadata-and-full-text-queries][advanced searching tutorial]], it would require using ~org-search-view~ with a query with specific regular expression syntax, like this:
|
|
|
|
#+BEGIN_EXAMPLE
|
|
+lisp +{^\*+\s-+TO-READ\s-}
|
|
#+END_EXAMPLE
|
|
|
|
But with ~org-ql-agenda~, you would write:
|
|
|
|
#+BEGIN_SRC elisp
|
|
(org-ql-agenda
|
|
(and (regexp "lisp")
|
|
(todo "TO-READ")))
|
|
#+END_SRC
|
|
|
|
** org-sidebar
|
|
|
|
This package is used by [[https://github.com/alphapapa/org-sidebar][org-sidebar]], which presents a customizable agenda-like view in a sidebar window.
|
|
|
|
* License
|
|
|
|
GPLv3
|
|
|
|
* Code :noexport:
|
|
|
|
Code used to update this document.
|
|
|
|
** Predicates
|
|
|
|
Generates the predicate subtree.
|
|
|
|
#+BEGIN_SRC elisp
|
|
(defun org-ql--readme-predicate-list ()
|
|
"Return an Org list string documenting predicates."
|
|
(concat "Arguments are listed next to predicate names, when applicable.\n\n"
|
|
(s-join "\n" (->> org-ql-predicates
|
|
(--sort (string< (symbol-name (plist-get it :name))
|
|
(symbol-name (plist-get other :name))))
|
|
(--map (-let* (((&plist :name name :docstring docstring :fn fn) it)
|
|
(args (->> (help-function-arglist fn)
|
|
(--remove (or (eq it '&rest)
|
|
;; Comparing the symbol itself doesn't work for some reason.
|
|
(string= (symbol-name it) "--cl-rest--"))))))
|
|
(if docstring
|
|
(progn
|
|
(setq docstring (s-replace "\n" " " docstring))
|
|
(format "+ ~%s%s~ :: %s" name
|
|
(if args
|
|
(format " %s" args)
|
|
"")
|
|
(unpackaged/docstring-to-org docstring)))
|
|
(warn "No docstring for: %s" name)
|
|
nil)))
|
|
-non-nil))))
|
|
|
|
(defun org-ql--readme-replace-node (outline-path string)
|
|
"Replace contents of node at OUTLINE-PATH with STRING."
|
|
(org-with-wide-buffer
|
|
(-let* ((subtree-marker (org-find-olp outline-path t))
|
|
((_headline element) (progn
|
|
(goto-char subtree-marker)
|
|
(org-element-headline-parser (point-max))))
|
|
((&plist :contents-begin beg :contents-end end) element))
|
|
(goto-char beg)
|
|
(delete-region (point) (1- end))
|
|
(insert string "\n"))))
|
|
|
|
(defun org-ql--readme-update-predicates ()
|
|
"Update predicate subtree in current document."
|
|
(interactive)
|
|
(org-ql--readme-replace-node '("Usage" "Predicates") (org-ql--readme-predicate-list)))
|
|
#+END_SRC
|