Re: org-scheduled-time-hour-regexp doesn't capture split repeats used by habit

[Bastien]

Hi Damian,

> The ':scheduled*' value for org-agenda-entry-types uses
> org-scheduled-time-hour-regexp to match related entries. The current 
> regexp doesn't match entries with split repeats like those used by
> habits- for example:   'SCHEDULED: <2019-06-25 Tue 20:30
> .+1d/2d>'. Because those entries show up in the agenda with a
> timestamp I believe they should be caught by the regexp.

thanks for reporting this, this is now fixed in the maint branch.

-- 
 Bastien

[O] org-scheduled-time-hour-regexp doesn't capture split repeats used by habit

[Damian]

The ':scheduled*' value for org-agenda-entry-types uses 
org-scheduled-time-hour-regexp to match related entries. The current 
regexp doesn't match entries with split repeats like those used by 
habits- for example:   'SCHEDULED: <2019-06-25 Tue 20:30 .+1d/2d>'. 
Because those entries show up in the agenda with a timestamp I believe 
they should be caught by the regexp.


org.el:
 (defconst org-scheduled-time-hour-regexp
  (concat "\\<" org-scheduled-string
  " *<\\([^>]+[0-9]\\{1,2\\}:[0-9]\\{2\\}[0-9+:hdwmy 
\t.-]*\\)>")
  "Matches the SCHEDULED keyword together with a time-and-hour 
stamp.")


Fix?
   (defconst org-scheduled-time-hour-regexp
  (concat "\\<" org-scheduled-string
  " *<\\([^>]+[0-9]\\{1,2\\}:[0-9]\\{2\\}[0-9+:hdwmy 
\t./-]*\\)>")
  "Matches the SCHEDULED keyword together with a time-and-hour 
stamp.")


Thanks,
-Damian