| commit | 566dac98b31180514aa14c24c60a20ffd8e10fc2 | |
| author | Carsten Dominik <carsten.dominik@gmail.com> | |
| Wed, 20 Jan 2010 10:43:52 +0000 (20 11:43 +0100) | ||
| committer | Carsten Dominik <carsten.dominik@gmail.com> | |
| Wed, 20 Jan 2010 10:43:52 +0000 (20 11:43 +0100) | ||
| tree | 967b7b0f6f56cd7b1b18e9253c80534dfe4a77e0 | treesnapshot (tar.gz zip) |
| parent | cae0c63c488067e93b665e9110dc74a634c52529 | commitdiff |
Autoload org-datetree-find-create-date
Stephen Eglen writes
> Within the agenda buffer, if I type 'i j' to jump to the current date I
> get:
>
> Debugger entered--Lisp error: (void-function org-datetree-find-date-create)
> org-datetree-find-date-create((1 20 2010))
> org-agenda-diary-entry-in-org-file()
> org-agenda-diary-entry()
> call-interactively(org-agenda-diary-entry nil nil)
>
> If I then do M-x load-library org-datetree
>
> and repeat 'i j', it works. Should this function be autoloaded?
Stephen Eglen writes
> Within the agenda buffer, if I type 'i j' to jump to the current date I
> get:
>
> Debugger entered--Lisp error: (void-function org-datetree-find-date-create)
> org-datetree-find-date-create((1 20 2010))
> org-agenda-diary-entry-in-org-file()
> org-agenda-diary-entry()
> call-interactively(org-agenda-diary-entry nil nil)
>
> If I then do M-x load-library org-datetree
>
> and repeat 'i j', it works. Should this function be autoloaded?
| lisp/ChangeLog | diffblobblamehistory | |
| lisp/org-agenda.el | diffblobblamehistory | |
| lisp/org-datetree.el | diffblobblamehistory |