-
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
Org 9.7 org-element
API changes break habit selector
#247
Comments
Hello, I don't understand. Please start from the beginning and explain the problem in context. As well, please provide a minimal reproducible example. And, of course, include the versions of all relevant software. You know, all the standard bug-report info. |
See also: alphapapa/org-ql#364 |
org-element
API changes break habit selector
I think i have the same issue, at least removing habit fixes it: Config in org-agenda-custom-commands:
Shows without debug:
Trace: https://gist.github.com/k11m1/fa6d819d247ef9e8b69d31bf0e659f2a Removing I am using Latest doom emacs (as of 2023-09-25), on Arch Linux.
|
@k11m1 Thanks. Until this is fixed, you'll have to either not use the habit selector, or use Org 9.6. |
@alphapapa No problem. I am not using the habit selector actively so disabling it for me fixed all the problems. |
Adam Porter ***@***.***> writes:
@k11m1 Thanks. Until this is fixed, you'll have to either not use the
habit selector, or use Org 9.6.
Another option is to comment out the check in org-element.el that causes
the issue.
|
Sure, just be sure to recompile that file afterward, otherwise you'll get reduced performance from its being interpreted. |
The root cause is emacs-straight/org-mode@f135954. Determining whether something is a habit will involve a call to The simple fix is to evaluate whether an item is a habit only I had a similar issue with a |
Please see https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=fac55324accbcab08dfebbde8295b2f1b4b9f45e, which demotes the error to a warning. |
Description
Opening the agenda (org-agenda) for the current week or day results in the backtrace shown below.
(C-c a a).
Custom agenda commands are only affected if they have habbits inside them.
I think the habbit
:habit t
selector triggers the bug.Environment
Org-Agenda and Super-Agenda setings
Notes:
Similar to alphapapa/org-web-tools#56 but for org-super-agenda.
Backtrace
The text was updated successfully, but these errors were encountered: