From: wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org (W. Greenhouse)
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [bug] org-agenda-diary-entry fails
Date: Tue, 19 Feb 2013 15:54:14 +0000 [thread overview]
Message-ID: <87obfg47vd.fsf@riseup.net> (raw)
In-Reply-To: 87bobgtzgd.fsf@ucl.ac.uk
Hi Eric,
Eric S Fraga <e.fraga-hclig2XLE9Zaa/9Udqfwiw@public.gmane.org> writes:
> Hello,
>
> with org up to date from git repository as of a few minutes ago, trying
> to insert a day diary entry from the agenda view
> (org-agenda-diary-entry) fails. Debug trace is attached.
>
> I cannot see what could be causing this problem. Any suggestions? I
> can start trying to bisect on recent changes.
>
> Thanks,
> eric
Does the `diary.org' file already exist with at least one headline in
it?
> Debugger entered--Lisp error: (error "Before first headline at position 1 in buffer diary.org")
> signal(error ("Before first headline at position 1 in buffer diary.org"))
> error("Before first headline at position %d in buffer %s" 1 #<buffer diary.org>)
> (condition-case nil (outline-back-to-heading invisible-ok) (error
> (error "Before first headline at position %d in buffer %s" (point)
> (current-buffer))))
Granted, this is an issue that the org-diary really should be able to
handle, but it's worth trying this again in a file with at least one
headline.
I am using a datetree-formatted org file that I'd already been using for
a while as an org-capture target before putting my diary entries there.
So far it's been okay.
Let me know how it goes,
--
WGG
GnuPG/PGP key: subkeys.gnupg.net 0D2D3F9E
next prev parent reply other threads:[~2013-02-19 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 9:39 [bug] org-agenda-diary-entry fails Eric S Fraga
2013-02-19 15:54 ` W. Greenhouse [this message]
2013-02-19 20:33 ` Eric S Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87obfg47vd.fsf@riseup.net \
--to=wgreenhouse-sgozh3hwpm2stnjn9+bgxg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).