Skip to content
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

Removed check for 'dotime in time-grid. #221

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tuh8888
Copy link

@tuh8888 tuh8888 commented Mar 18, 2022

Possible fix for #212

Might be a naive solution, but I'm not sure what the check for 'dotime is supposed to account for. This solved the issue for my configuration and use-case. I'm not sure how your testing framework works in order to see if I've messed anything else up that you've already thought of though.

@alphapapa
Copy link
Owner

Well, as you can see from the removed comment, that code was added by necessity after much research and testing of the org-agenda code's output. While removing it might fix the TODO search in your case, it would probably also break other agenda/search types, which is the main use case for this package. I couldn't merge this unless it could be confirmed that 1) Org has changed something and doesn't use this text property anymore, and 2) the Org version in which such a change happened is the minimum supported by this package (which wouldn't be likely to happen for some time).

@tuh8888
Copy link
Author

tuh8888 commented Mar 28, 2022

Unfortunately, I don't know what testing you've done to be able to tell when you needed the dotime check. Maybe another org-super-agenda--defgroup could be added which doesn't include the dotime check of time-grid? I spent a long time trying to figure out how to get around time-grid's greediness, thinking I was misunderstanding something about its behavior or the query language, before implementing this fix. At least some documentation that this is a potential pitfall might be nice if you understandably don't want to potentially break time-grid's functionality for users of older versions of org-agenda.

On another note, I really appreciate the work you've put into this package, and it fits heavily into my daily workflow. I apologize for not being able to offer a more nuanced solution to this problem you obviously spent a while considering already. Maybe some day I'll be able to take the time to examine org-agenda's usage of the dotime property to figure out a better solution for this issue.

@alphapapa
Copy link
Owner

alphapapa commented Sep 23, 2023

Fixing this will require some research and testing to confirm that nothing else gets broken.

In the meantime, I can recommend using org-ql as an alternative to using the Org Agenda "all TODOs" view.

@tuh8888 Thanks for the kind words.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants