emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: Simon Campese <emacs-orgmode@campese.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Non-interactive insertion of future-dates
Date: Wed, 25 Jan 2012 12:56:37 -0500	[thread overview]
Message-ID: <CAHRqSkSBEWFEygxzbnbycbk416eZnZ3GJ1HUKf8oF1LGUyYrMw@mail.gmail.com> (raw)
In-Reply-To: <87sjj3d98v.fsf@rman-office.uni.lux>

Hello,


On Wed, Jan 25, 2012 at 11:42, Simon Campese <emacs-orgmode@campese.de> wrote:
>
> Dear community,
>
> I want to setup a capture-template that sets a
> SCHEDULE-property in the future (say one week from today) without any
> user interaction.
>
> Currently, I almost achieve this by inserting the line
>
> :SCHEDULED: <%(org-read-date nil nil nil nil nil "+1w")>
>
> into my template. When I now call the template, I end up in the
> date-time-prompt, with "+1w" prefilled, so that manually have to press
> enter.
>
> Maybe it is trivial to call an interactive lisp-function and emulate
> some keypress, in which case I would be thankful for the code that
> achieves this (my lisp-skills are limited). Also, one should be able to
> achieve what I want by using format-time-string and increment the
> current time, but again my lisp-skills prohibit me from implementing it
> myself.

A similar question had come up on StackOverflow (
http://stackoverflow.com/questions/7986935/using-org-capture-templates-to-schedule-a-todo-for-the-day-after-today/7988809#7988809
).

My answer there should apply, adjusting the offset from +1d to +1w :

    SCHEDULED: %(org-insert-time-stamp (org-read-date nil t \"+1d\"))

Alternately you can include the SCHEDULED: portion within the
timestamp insertion itself.  This example will also include a fixed
time at which to schedule the item (unneeded in this case I suspect
but it could be of use elsewhere) :

    (org-insert-time-stamp (org-read-date nil t \"+1w 12:00\") t nil
\"SCHEDULED: \")

> In any case, it might be a good idea to include non-interactive access
> to relative times in template expansion, so that for example one
> can state something like %t[+1w] or %{+1w}t in the template to get the
> date one week from today (one should spend some more time to specify the
> actual input-format of course...). What do you think?

I agree, adding the ability to automatically have relative dates would
allow for quicker capture templates if you regularly need to to set
them with a specific offset.

> Thank you very much,
>
> Simon

Regards,

Jonathan

  parent reply	other threads:[~2012-01-25 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 16:42 Non-interactive insertion of future-dates Simon Campese
2012-01-25 17:37 ` Borbus
2012-01-28 17:42   ` Simon Campese
2012-01-25 17:56 ` Jonathan Leech-Pepin [this message]
2012-01-28 22:38   ` Simon Campese

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=CAHRqSkSBEWFEygxzbnbycbk416eZnZ3GJ1HUKf8oF1LGUyYrMw@mail.gmail.com \
    --to=jonathan.leechpepin@gmail.com \
    --cc=emacs-orgmode@campese.de \
    --cc=emacs-orgmode@gnu.org \
    /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).