Agenda broken after update to 9.1

Agenda broken after update to 9.1

[Loris Bennett]

Hi,

I have just updated to 9.1 from whatever version was current on ELPA
last week.  When I noe try to generate the agenda I get the following
error:

  Press key for agenda command:
  org-agenda-list: Wrong type argument: listp, #("----------------" 0 16 (org-heading t))

Any ideas what the problem might be?

Cheers,

Loris

-- 
This signature is currently under construction.

Re: Agenda broken after update to 9.1

[Loris Bennett]

"Loris Bennett" <loris.bennett@fu-berlin.de> writes:

> Hi,
>
> I have just updated to 9.1 from whatever version was current on ELPA
> last week.  When I noe try to generate the agenda I get the following
> error:
>
>   Press key for agenda command:
>   org-agenda-list: Wrong type argument: listp, #("----------------" 0 16 (org-heading t))
>
> Any ideas what the problem might be?

The culprit seems to be this:

  * Repeating Event
    <2016-02-17 Wed 11:00-12:30 +1w>

If I remove the '+1w' then the error goes away.  If I then change the
date today:

  * Repeating Event
    <2017-09-06 Wed 11:00>

I get the error again.  If I change the date to yesterday:

  * Repeating Event
    <2017-09-05 Tue 11:00>

the error goes away.

Cheers,

Loris

-- 
This signature is currently under construction.

Re: Agenda broken after update to 9.1

[Nicolas Goaziou]

Hello,

"Loris Bennett" <loris.bennett@fu-berlin.de> writes:

> I have just updated to 9.1 from whatever version was current on ELPA
> last week.  When I noe try to generate the agenda I get the following
> error:
>
>   Press key for agenda command:
>   org-agenda-list: Wrong type argument: listp, #("----------------" 0 16 (org-heading t))

See ORG-NEWS > Incompatible changes > Change order of items in ~org-agenda-time-grid~

Regards,

-- 
Nicolas Goaziou

Re: Agenda broken after update to 9.1

[Loris Bennett]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> "Loris Bennett" <loris.bennett@fu-berlin.de> writes:
>
>> I have just updated to 9.1 from whatever version was current on ELPA
>> last week.  When I noe try to generate the agenda I get the following
>> error:
>>
>>   Press key for agenda command:
>>   org-agenda-list: Wrong type argument: listp, #("----------------" 0 16 (org-heading t))
>
> See ORG-NEWS > Incompatible changes > Change order of items in ~org-agenda-time-grid~
>

OK, thanks.  After removing the customisation for org-agenda-time-grid,
the agenda is generated.

However, when I try to clock into the first of several entries in the
agenda, I get the error

  org-duration-to-minutes: Invalid duration format: ""

and am not clocked in.  If I try the same entry a second time, there is
no error and I am clocked in.  Switching between clocks other than that
for the first entry work fine.

Any ideas what the problem here might be?

Cheers,

Loris

-- 
This signature is currently under construction.

Re: Agenda broken after update to 9.1

[Nicolas Goaziou]

Hello,

"Loris Bennett" <loris.bennett@fu-berlin.de> writes:

> However, when I try to clock into the first of several entries in the
> agenda, I get the error
>
>   org-duration-to-minutes: Invalid duration format: ""
>
> and am not clocked in.  If I try the same entry a second time, there is
> no error and I am clocked in.  Switching between clocks other than that
> for the first entry work fine.

I think I fixed it in maint. Could you confirm it?

Thank you.

Regards,

-- 
Nicolas Goaziou

Re: Agenda broken after update to 9.1

[Loris Bennett]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> "Loris Bennett" <loris.bennett@fu-berlin.de> writes:
>
>> However, when I try to clock into the first of several entries in the
>> agenda, I get the error
>>
>>   org-duration-to-minutes: Invalid duration format: ""
>>
>> and am not clocked in.  If I try the same entry a second time, there is
>> no error and I am clocked in.  Switching between clocks other than that
>> for the first entry work fine.
>
> I think I fixed it in maint. Could you confirm it?

Assuming I did everything correctly, I can confirm that the problem is
resolved in the following version:

  Org mode version 9.1 (release_9.1-21-g6cfc7c @ /home/loris/git/org-mode/lisp/)

Thanks for the new release and all your efforts.

Loris
-- 
This signature is currently under construction.