emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mikael Fornius <mfo@abc.se>
To: emacs-orgmode@gnu.org
Subject: Diary sexps in agenda
Date: Fri, 20 Feb 2009 11:29:10 +0100	[thread overview]
Message-ID: <87k57l8kqx.fsf_-_@abc.se> (raw)
In-Reply-To: <87skma8hkg.fsf@abc.se> (Mikael Fornius's message of "Thu, 19 Feb 2009 18:25:35 +0100")

(The patch is wrong, I had misunderstood, as I suspected, sorry.)

The problem was that I used < and > around the diary sexp when you
apparently should not.

You can but then the line after the sexp is not showed in the agenda.

It works correct if %%(...) is at beginning of line, with no <> braces.

But I first only knew of 

(info "(org) timestamps")

that says that you shound surround with <>. I later found the page

(info "(org) Weekly/Daily agenda")

who says not to, this maybe needs to be updated?

Or is this the intended behavior?

I think would best if agenda could handle both cases nicely. If you
think that it should be so I can give it another try, beware. :-)


Mikael Fornius

  reply	other threads:[~2009-02-20 10:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19 15:27 [PATCH] Makes diary sexps appear correct in agenda views Mikael Fornius
2009-02-19 17:25 ` Mikael Fornius
2009-02-20 10:29   ` Mikael Fornius [this message]
2009-02-20 10:05 ` Carsten Dominik
2009-02-20 10:35   ` Mikael Fornius

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:

  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=87k57l8kqx.fsf_-_@abc.se \
    --to=mfo@abc.se \
    --cc=emacs-orgmode@gnu.org \


* 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


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).