From: Michael Heerdegen <michael_heerdegen@web.de>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Headline generation as in diary?
Date: Wed, 02 Sep 2020 15:45:36 +0200 [thread overview]
Message-ID: <87mu28l2bj.fsf@web.de> (raw)
In-Reply-To: <m2lfhsd5yq.fsf@gmail.com> (Robert Pluim's message of "Wed, 02 Sep 2020 08:54:05 +0200")
Robert Pluim <rpluim@gmail.com> writes:
> How about:
>
> diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
> index 78fe13303..9049b3a42 100644
> --- a/lisp/org-agenda.el
> +++ b/lisp/org-agenda.el
> @@ -5772,7 +5772,7 @@ displayed in agenda view."
> r (replace-match "" nil nil r)))
> (if (string-match "\\S-" r)
> (setq txt r)
> - (setq txt "SEXP entry returned empty string"))
> + (setq txt (org-no-properties (org-get-heading t t t t))))
> (setq txt (org-agenda-format-item extra txt level category tags 'time))
> (org-add-props txt props 'org-marker marker
> 'date date 'todo-state todo-state
Thanks for looking at this.
Ok - That gives me a headline in the agenda, but a wrong one (more or
less, a random headline in the same file, at a seemingly unrelated
location).
> (Iʼm guessing yet-another-config-variable is unnecessary)
I think so toom yes.
> >> You can use them in timestamps as well, which is useful for
> >> weird time
> >> periods
> >>
> >> ** Just before midnight on a few days 23:00-24:00
> >> <%%(org-block 2020 8 31 2020 9 2)>
> >> <%%(org-block 2020 9 10 2020 9 12)>
>
> Michael> But it seems those time stamps are not allowed to span
> Michael> multiple lines
> Michael> (at least I don't get it work). Seems org doesn't
> Michael> recognize them as
> Michael> such?
>
> Itʼs working fine for me in org-9.3.6. Note that I have my default
> agenda view set to a fortnight, and those dates span two different
> weeks.
I didn't mean time spans. What doesn't work for me are time _stamps_
that span multiple text lines.
Thanks,
Michael.
next prev parent reply other threads:[~2020-09-02 13:47 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 [this message]
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
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=87mu28l2bj.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-orgmode@gnu.org \
--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).