I might be having the same problem as Upgrading to org-mode 9.1.6 error: org-duration-to-minutes: Invalid duration format: "val" . I really am lost. I also get Invalid duration format: "+0:30" . And I just can't figure out which entry is causing the trouble. There is no :effort: entry in the file that is causing the trouble. If I exclude that file from my agenda files I can view an agenda (of course, with all the information missing from that one file). There is also no +0 something that might be causing that. I do not use AM or PM. And I fear I might have to comment all the lines and try for each line whether it's causing that trouble. And I really would like to be able to just see my calendar for tomorrow. Is there any way to search faster than this manual search?
Emacs Stack Exchange is a question and answer site for those using, extending or developing Emacs. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
Anybody can answer
The best answers are voted up and rise to the top
(setq debug-on-error t)you will get a lisp backtrace that should provide more context on which entry is causing the issue. – rpluim May 12 '20 at 17:49M-x org-lintis always my first choice for data problems like this, but I don't think it's going to help in this case - you might try it anyway. My second choice would be at look at the file very carefully: are you sure you cannot see a+0:30? My third choice would be to reload Org mode uncompiled ` C-u M-x org-reload <RET>, ([edebug](https://www.gnu.org/software/emacs/manual/html_node/elisp/Edebug.html#Edebug) the functionorg-duration-to-minutes` and try generating the agenda: ... – NickD May 12 '20 at 18:07durationargument withe duration RET. If it looks OK, just continue withcand keep examining the variable every time it stops, until you get your "+0:30". When you do, generate a backtrace withdand either add it to your question if you need help or figure out how to read it and determine the suspect entry. – NickD May 12 '20 at 18:07