From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Michael Welle <mwe012008@gmx.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to set the scheduled property programmatically?
Date: Wed, 25 Jan 2017 23:30:05 +0100 [thread overview]
Message-ID: <878tpybwnm.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87d1fg8fey.fsf@luisa.c0t0d0s0.de> (Michael Welle's message of "Sat, 21 Jan 2017 18:57:09 +0100")
Hello,
Michael Welle <mwe012008@gmx.net> writes:
> what is the correct way to set the property? I tried
>
> (org-entry-put pom "SCHEDULED" "<2017-01-01 Sun ++1w>")
>
> which results in
>
> SCHEDULED: <2017-01-01 Sun>
>
> As you can see, the 'repeater' is missing.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-01-25 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 17:57 How to set the scheduled property programmatically? Michael Welle
2017-01-22 14:12 ` Michael Welle
2017-01-25 22:30 ` Nicolas Goaziou [this message]
2017-01-26 10:14 ` Michael Welle
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=878tpybwnm.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mwe012008@gmx.net \
/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).