Richard Lawrence writes:
> Hi everyone,
>
> Richard Lawrence writes:
>
>> I can now confirm that this is the problem. It looks like what is happening
>> here
>> is that the regex is meant to match a time range, but ends up matching
>> the date: thus a string like "12-31 13:00" gets mangled to "1
Hi everyone,
Richard Lawrence writes:
> I can now confirm that this is the problem. It looks like what is happening
> here
> is that the regex is meant to match a time range, but ends up matching
> the date: thus a string like "12-31 13:00" gets mangled to "12 13:00"
> and sent into org-read-da
Richard Lawrence writes:
> This is org 9.4 running from maint (commit ab00524fc). I spent a while
> stepping through org-capture and org-read-date but haven't found the
> problem yet. I suspect this snippet from a cond form in the middle of
> org-capture-set-target-location:
>
> #+begin_src
>
Hi all,
I ran into a subtle bug yesterday. Basically, when using org-capture to
capture
- an entry into a datetree,
- on a date other than today (using :time-prompt in org-capture-templates)
- with a capture template that inserts a timestamp (%T)
then I get incorrect results for either the
