Re: [O] Filtering org-clock-display

[Noah Slater]

I'm getting an error on HEAD now:

Debugger entered--Lisp error: (void-function org-add-props)

  (org-add-props "WARNING: No org-loaddefs.el file could be found from where org.el is loaded." nil (quote face) (quote org-warning))

  (message (org-add-props "WARNING: No org-loaddefs.el file could be found from where org.el is loaded." nil (quote face) (quote org-warning)))

  (condition-case nil (load (concat (file-name-directory load-file-name) "org-loaddefs.el") nil t t t) (error (message (org-add-props "WARNING: No org-loaddefs.el file could be found from where org.el is loaded." nil (qu$

  (or (equal this-command (quote eval-buffer)) (condition-case nil (load (concat (file-name-directory load-file-name) "org-loaddefs.el") nil t t t) (error (message (org-add-props "WARNING: No org-loaddefs.el file could b$

  eval-buffer(#<buffer  *load*-416952> nil "/Users/nslater/.emacs.d/vendor/org-mode/lisp/org.el" nil t)  ; Reading at buffer position 3681

  load-with-code-conversion("/Users/nslater/.emacs.d/vendor/org-mode/lisp/org.el" "/Users/nslater/.emacs.d/vendor/org-mode/lisp/org.el" nil t)

  require(org)

  eval-buffer(#<buffer  *load*-693116> nil "/Users/nslater/.emacs.d/lisp/init-org.el" nil t)  ; Reading at buffer position 127

  load-with-code-conversion("/Users/nslater/.emacs.d/lisp/init-org.el" "/Users/nslater/.emacs.d/lisp/init-org.el" nil t)

  require(init-org)

  eval-buffer(#<buffer  *load*> nil "/Users/nslater/.emacs.d/init.el" nil t)  ; Reading at buffer position 2043

  load-with-code-conversion("/Users/nslater/.emacs.d/init.el" "/Users/nslater/.emacs.d/init.el" t t)

  load("/Users/nslater/.emacs.d/init" t t)

  #[0 "^H\205\262^@     address@hidden;^@ address@hidden;address@hidden@\316\202;address@hidden:address@hidden;address@hidden@\324\325\32$

  command-line()

  normal-top-level()

On 30 May 2014 14:15, Bastien <address@hidden> wrote:

Hi Noah,

Noah Slater <address@hidden> writes:

> That's pretty cool. Any reason it doesn't use the same syntax as the
> :tstart param though?

I first want to see if the new feature is useful before adding up more
subfeatures.  So let's wait until 8.3 is released and see if (more)
people want more flexibility here.  In the meantime, I think it makes
sense to offer the predefined ranges that we can use in org clock
tables.

> This breaks a function I had written (and perhaps other people's
> functions).

This is now fixed, thanks,

--
 Bastien