Am 04.07.2013 22:15, schrieb Bastien:
> Hi Rainer,
>
> This should now be fixed, thanks.
>
Confirmed!
Thanks!
Hi Rainer,
This should now be fixed, thanks.
--
Bastien
Am 04.07.2013 17:12, schrieb Bastien:
> Rainer Stengele writes:
>
>> Lisp error is triggered by the SETUPFILE option:
>>
>> #+SETUPFILE: ~/org/GLOBAL_SETUP_DIPLAN.org
>>
>> If I remove that line everything works fine.
> Can you copy and past lines starting with "#+" from
> GLOBAL_SETUP_DIPLAN.org?
Rainer Stengele writes:
> Lisp error is triggered by the SETUPFILE option:
>
> #+SETUPFILE: ~/org/GLOBAL_SETUP_DIPLAN.org
>
> If I remove that line everything works fine.
Can you copy and past lines starting with "#+" from
GLOBAL_SETUP_DIPLAN.org?
Parsing those lines is where the error probably
Am 04.07.2013 16:11, schrieb Bastien:
> Please send a recipe: a step-by-step way of reproducing the problem,
> with minimal config and org file.
>
Found it:
Lisp error is triggered by the SETUPFILE option:
#+SETUPFILE: ~/org/GLOBAL_SETUP_DIPLAN.org
If I remove that line everything works fine.
Please send a recipe: a step-by-step way of reproducing the problem,
with minimal config and org file.
--
Bastien
Am 04.07.2013 16:07, schrieb Bastien:
> Hi Rainer,
>
> Rainer Stengele writes:
>
>> I pulled today and since then run into this issue after starting an
>> agenda:
> Can you give a recipe?
>
> Thanks,
>
("01" "agenda - prio A,B todos - sorted prio up - today" ;;
(
;; show ONGOING t
Hi Rainer,
Rainer Stengele writes:
> I pulled today and since then run into this issue after starting an
> agenda:
Can you give a recipe?
Thanks,
--
Bastien
Going back to
git checkout f0c2a680568009ad2f93020af8134dbd481070e2
works again, so I assume it could be the following commit.
Rainer
Am 04.07.2013 15:35, schrieb Rainer Stengele:
> All,
>
> I pulled today and since then run into this issue after starting an agenda:
>
> Please help!
>
> Rai
