If I try to jump (using "j") in org-agenda to the month September, it sometimes takes me to January. I am using org 9.4.4. If I type any of these configurations, I am still going to January:


If I type:


I go to September. Is this a bug?

  • 1
    Probably - there's been some churn in the parse-time-string function in the past year to make it grok ISO 8601 dates and the old RFC 822(ish) implementation was put into a subfunction. It may well be that something got broken in the process. Note that if it is a bug, it is an Emacs bug: use report-emacs-bug to report it. – NickD Jan 15 at 15:51
  • 1
    on a quick check it looks that if it cannot complete (whatever it means to org-read-date) defaults on current date, and that's why you still get january. I'll try to take a deeper look later if no one gets it going. – Muihlinn Jan 15 at 16:24
  • @Muihlinn: try (parse-time-string "sep") vs (parse-time-string "sept") – NickD Jan 15 at 17:20
  • 1
    @NickD yep, but I'm not sure if it's a bug or just something in the org-read-date code or documentation. Look @ var parse-time-months it has sep and september, nothing in-between, although not that I'm familiar with emacs parse time libs, so I may be wrong. – Muihlinn Jan 15 at 17:32

Following comments, it doesn't looks like a bug to me, parse-time-months contains "sep" and "september" nothing in between. If org-read-date cannot parse what you give defaults to current date (in use).

As further reference Org manual says:

The function understands English month and weekday abbreviations. If you want to use un-abbreviated names and/or other languages, configure the variables parse-time-months and parse-time-weekdays

So it is the expected behavior and I assume that there are some typos in the examples, either in the manual itself as well in the org-read-date docstring.

  • 1
    See The Date/Time prompt: the example ‘22 sept 0:34’ ⇒ 2006-09-22 0:34 does not work any longer. It's almost certainly a change - whether it's a bug or not is debatable, but I think a bug report is indicated just to make sure. Of course, the example may be wrong. – NickD Jan 15 at 19:08
  • @NickD I agree, the org manual page itself is somewhat contradictory. – Muihlinn Jan 15 at 19:26
  • I think you are right: I've looked at the git log of parse-time.el and I don't see any changes that would limit the set of month abbreviations accepted. I also tested it back with emacs 24.3.1 and it exhibits the same behavior, so there was no change. The example in the Date/Time prompt page is wrong. – NickD Jan 15 at 20:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.