There was no year zero, agenda -bug/feature

There was no year zero, agenda -bug/feature

[Jacob Toft Pedersen]

[-- Attachment #1.1: Type: text/plain, Size: 811 bytes --]

Hi

  I had kept a backup of my .emacs file in an orgfile. 

  But running the org-agenda, would malfuntion, stating "byte-code:
  There was no year zero" and the agenda view would not work.

  I have been able to track it down to the following offending piece
  of code. Its a piece of my .emacs
<snippet>


(setq org-remember-templates
      '(
      	("Birthday" ?f "* %^{Navn} :birthday: \n SCHEDULED: <%^{år
(YYYY)}-%^{måned (MM)}-%^{dag (DD)} +1y>  %!" "~/orgfiles/birthdays.org"
"" )
	)
      )

</snippet>


  I dont know if its a bug, it feels that way, but i might be
  expecting to much from org-mode. As its indeed a malformed
  "SCHEDULED:" statement, but not meant to be interpreted as one.




-- 
Med venlige hilsner
Jacob Toft Pedersen
http://rotand.dk/blog

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: There was no year zero, agenda -bug/feature

[Bernt Hansen]

Jacob Toft Pedersen <jacob@rotand.dk> writes:

>   I had kept a backup of my .emacs file in an orgfile. 
>
>   But running the org-agenda, would malfuntion, stating "byte-code:
>   There was no year zero" and the agenda view would not work.
>
>   I have been able to track it down to the following offending piece
>   of code. Its a piece of my .emacs
> <snippet>
>
>
> (setq org-remember-templates
>       '(
>       	("Birthday" ?f "* %^{Navn} :birthday: \n SCHEDULED: <%^{år
> (YYYY)}-%^{måned (MM)}-%^{dag (DD)} +1y>  %!" "~/orgfiles/birthdays.org"
> "" )
> 	)
>       )
>
> </snippet>
>
>
>   I dont know if its a bug, it feels that way, but i might be
>   expecting to much from org-mode. As its indeed a malformed
>   "SCHEDULED:" statement, but not meant to be interpreted as one.

Can you block out the entire file with 

#+begin_src elisp
...
#+end_src

Maybe that will help?

-Bernt