emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mikael Fornius <mfo@abc.se>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Makes diary sexps appear correct in agenda views.
Date: Thu, 19 Feb 2009 18:25:35 +0100	[thread overview]
Message-ID: <87skma8hkg.fsf@abc.se> (raw)
In-Reply-To: <87wsbm8n0i.fsf@abc.se> (Mikael Fornius's message of "Thu, 19 Feb 2009 16:27:57 +0100")

(I reply my own post.)

When giving the problem a second thougt I realize that there may be
something to it that I do no understand fully.

The <%%(-sexps has worked properly before in earlier versions of org and
the regexp

> -	 (regexp "^&?%%(")

makes me think that there is more because I find the ampersand hard to
understand or motivate.

My patch works for me but maybe there is something else to it.

If it is so that the agenda should be able to read and interpret emacs
calendar ~/diary file also?, then my suggested patch is no good solution.

Mikael Fornius

  reply	other threads:[~2009-02-19 17:25 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 [this message]
2009-02-20 10:29   ` Diary sexps in agenda Mikael Fornius
2009-02-20 10:05 ` [PATCH] Makes diary sexps appear correct in agenda views 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=87skma8hkg.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).