From: "Colin Baxter 😺" <m43cap@yandex.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: org-diary
Date: Wed, 03 Nov 2021 09:34:05 +0000 [thread overview]
Message-ID: <875yt960s2.fsf@yandex.com> (raw)
In-Reply-To: <87tugtfwi9.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 03 Nov 2021 08:56:14 +0000")
>>>>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Wednesday, 3 Nov 2021 at 06:43, Colin Baxter 😺 wrote:
>> I have this
>>
>> #+begin_src elisp &%%(org-diary :deadline* :timestamp
>> :scheduled*) #+end_src
> I cannot help you directly but I do note that my equivalent entry
> in my Emacs diary file is subtly different:
> %%(org-diary :scheduled :timestamp) ~/s/notes/diary.org
> No &, no *s, and a file name at the end. Having said this, I must
> admit that I cannot find any documentation on the format of this
> line in the info manual. Maybe it's hiding...
Thanks Eric. You have reminded me about the file name. I don't have a
file name at the end because I want all my 5 agenda files searched.
However, by entering each file in turn I can now identify the particular
agenda file that's causing the warning. I don't see anything immediately
wrong with it, but it contains multiple schedules with + and - days. I
suspect the problems lies somewhere there.
Thanks again - a great post that jogged my memory.
Best wishes, Colin.
next prev parent reply other threads:[~2021-11-03 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 6:43 org-diary Colin Baxter 😺
2021-11-03 8:56 ` org-diary Eric S Fraga
2021-11-03 9:34 ` Colin Baxter 😺 [this message]
2021-11-03 11:04 ` org-diary Eric S Fraga
2021-11-04 15:56 ` org-diary Michael Maurer
2021-11-04 16:05 ` org-diary Eric S Fraga
2021-11-04 17:21 ` org-diary Michael Maurer
2021-11-05 12:14 ` org-diary Eric S Fraga
2021-11-05 12:56 ` org-diary Colin Baxter 😺
2021-11-05 13:12 ` org-diary Eric S Fraga
[not found] ` <87lf24odbl.fsf_-_@riseup.net>
[not found] ` <87ilx8e3zc.fsf@ucl.ac.uk>
2021-11-06 0:26 ` your latest paper will not allow eww Quiliro Ordóñez
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=875yt960s2.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=emacs-orgmode@gnu.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).