Sorry, I was being dumb. All fine. To prevent further breakage, I am attaching a doc fix. I hope it is useable?
Cheers, Simon On 11/06/2012 11:21 PM, Simon Thum wrote:
Dear all, I have a sexp entry that somehow works "less good" now. It's ** 11:00 Monthly PTB Telco %%(org-float t 2 3) (some more stuff) The agenda reads "SEXP entry returned empty string", whereas previously I got the headline. Putting something behind the sexp get me that, but the time is not recovered. I think this matches the example in the manual quite closely, so probably it's a bug. Any ideas? I'm on the current git but I don't update too regularly and it was broken before. Cheers, Simon
>From 247c3fdde300be13d20e591ca5f217ad0385de49 Mon Sep 17 00:00:00 2001 From: Simon Thum <simon.t...@gmx.de> Date: Sun, 26 Aug 2012 19:37:44 +0200 Subject: [PATCH] document another sexp timestamp syntax TINYCHANGE --- doc/org.texi | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/doc/org.texi b/doc/org.texi index bf67876..30c1ce4 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -5571,6 +5571,15 @@ example with optional time <%%(org-float t 4 2)> @end example +A similar syntax that is different in terms of agenda results is + +@example +* Wife +%%(org-anniversary 2001 05 07) Wedding day (%d Years) +@end example + +Here, ``Wedding day (n Years)'' will show up in the agenda (if the headline matches). It is important that there is no leading space. + @item Time/Date range @cindex timerange @cindex date range -- 1.7.8.6
