emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>,
	Robert Pluim <rpluim@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Headline generation as in diary?
Date: Thu, 03 Sep 2020 21:35:54 +0800	[thread overview]
Message-ID: <875z8vm18l.fsf@localhost> (raw)
In-Reply-To: <87zh67j92p.fsf@web.de>

> When dealing with complicated date rules it can likely happen that a
> diary sexp doesn't fit into one line.

Diary sexp can be a user-defined function. If your sexp needs to span
multiple lines, it is probably worth defining a function and simply
using <%%(your-function)> as a timestamp.

Best,
Ihor

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Robert Pluim <rpluim@gmail.com> writes:
>
>> I can push my change to org, but Iʼm not a regular org contributor, so
>> Iʼd prefer to hear from one of the maintainers first.
>
> Sorry - I meant, I see no reason to touch the existing code.  No need to
> change anything for what I want.
>
>>     Michael> This doesn't work:
>>
>>     Michael> | ** APPT 17:00 Test
>>     Michael> | SCHEDULED: <%%(and (or (diary-date 03 09 2020)
>>     Michael> |                        (diary-date 04 09 2020)))>
>
>> I think thatʼs just a consequence of timestamps not being allowed to
>> span multiple lines in org, unlike diary.
>
> This is bad.  Why is that?  Can it be changed?
>
> When dealing with complicated date rules it can likely happen that a
> diary sexp doesn't fit into one line.
>
> Regards,
>
> Michael.


  reply	other threads:[~2020-09-03 13:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 14:34 Headline generation as in diary? Michael Heerdegen
2020-09-01 15:10 ` Eric S Fraga
2020-09-01 15:18   ` Michael Heerdegen
2020-09-01 15:28     ` Michael Heerdegen
2020-09-01 16:10     ` Robert Pluim
2020-09-01 16:17       ` Eric S Fraga
2020-09-01 16:51         ` Robert Horn
2020-09-01 21:56       ` Michael Heerdegen
2020-09-02  6:54         ` Robert Pluim
2020-09-02 13:45           ` Michael Heerdegen
2020-09-02 15:00             ` Robert Pluim
2020-09-02 22:51               ` Michael Heerdegen
2020-09-03  7:14                 ` Robert Pluim
2020-09-03 13:14                   ` Michael Heerdegen
2020-09-03 13:35                     ` Ihor Radchenko [this message]
2020-09-03 14:01                       ` Michael Heerdegen
2020-09-03 15:31                         ` Ihor Radchenko
2020-09-03 17:01                           ` Michael Heerdegen
2020-09-03 18:04                             ` Ihor Radchenko
2020-09-03 18:37                               ` Michael Heerdegen
2020-09-03 14:06                       ` Robert Pluim
2020-09-03 14:46                         ` Michael Heerdegen
2020-09-03 15:17                           ` Robert Pluim
2020-09-03 15:34                         ` Ihor Radchenko
2020-10-28 17:12 ` Michael Heerdegen

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=875z8vm18l.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=rpluim@gmail.com \
    /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).