Add notes

notes.org

@@ -6,6 +6,16 @@
 
 [2017-12-31 Sun 17:54]  I wonder if, instead of parsing the whole buffer with =org-element-parse-buffer=, we could simply work on a list of heading positions, e.g. a loop would search forward to the next heading position, then call whatever predicates it needed at the heading's position, using =save-excursion= around each function call.  The predicates would need to be updated to get their data from the buffer, instead of using =org-element-property=, but that wouldn't be hard.
 
+** Byte-compile lambdas
+
+=elfeed-search--update-list= byte-compiles lambdas returned by =elfeed-search-compile-filter=.  Maybe I could do something like this too.
+
+If I can get this working, I should profile it to see what difference it makes.
+
+** Use macros for =date=
+
+If I made the =date= selector a macro, I could avoid the need to quote the comparator.
+
 * Examples / testing
 
 #+BEGIN_SRC elisp
@@ -20,6 +30,7 @@
     (and (or (date :deadline '<= (org-today))
              (date :scheduled '<= (org-today)))
          (not (apply #'todo org-done-keywords-for-agenda))))
+
   (org-agenda-ng "~/org/main.org"
     (and (or (date :deadline '<= (org-today))
              (date :scheduled '<= (org-today)))