-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
:discard
breaks org-agenda-redo when processing the time grid
#215
Comments
Rubber-ducking this a little. I /think/ it trying to discard the non-header lines from the agenda view and discard them, but it's reading them as strings and not org elements. the
If this intuition is correct, then I would expect this to be a bug with a simple fix of swallowing the error when discarding in a time-grid (with more or less work done verifying that the discard is happening in a time grid). Looking at the codebase, however, I have no idea how to start tackling this problem. I think this also means there must be a more convenient way to discard events this way. I, personally, couldn't figure this out from the documentation so if this is expected behavior please let me know and I can submit an update to the README. Attempting to work in an org-super-agenda-only mode returns the same error with the following configuration: ("x" "Overview/span1"
((agenda ""
((org-super-agenda-groups
`((:discard (:deadline (before ,(org-read-date nil nil "-1d")) ))
(:discard (:deadline (after ,(org-read-date nil nil "+1d")) ))
))))
)) |
:discard (after "<date>")
:discard
breaks org-agenda-redo when processing the time grid
Thanks for reporting this. I probably won't have time to debug this soon, so patches welcome. |
I have the following configuration at the top level of my configs (I removed irrelevant agenda commands, so beware of unbalanced parens).
This configuration works on the first load; however, when I refresh the page, I get the following stack trace (from
emacs --debug-init
) which crashes my agenda view.I am currently using org-super-agenda at the current head of master: fb5e2ef.
I understand that relative date support is in the hands of the user (re: #59) -- as an elisp novice, I could easily be doing something wrong. Any help with this bug or my configuration would be appreciated!
The text was updated successfully, but these errors were encountered: