emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nathan Neff <nathan.neff@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Templates for cloning
Date: Thu, 2 Aug 2012 12:12:51 -0500	[thread overview]
Message-ID: <CAC=HedDJuf6AMXXXZKNbSKe9O6-3oWJeCQCc_z7wq1vOkSg-Bg@mail.gmail.com> (raw)

Hi all,

Is there a way to create a template structure for cloning?

The main purpose would be to create a shell or structure that is easy
to replicate,
such as a workflow, etc.  This shell, etc would not need any
hard-coded dates, but could
simply have offsets for sub-items whose due-dates or start dates are
relative to a single start date.

For example,

I'd like to have this:

* Some Project
** Plan Project
<start-date-placeholder>
** Step 1
<start-date-placeholder +1d>
** Step 2

<start-date-placeholder +1w>
** Project Due
<DEADLINE:start-date-placeholder +1m>

This would be cool, because

1)  You wouldn't see this template in the agenda, because the dates
aren't hard-coded
2)  You could be prompted for the start date when you clone this
template, and all the dates
would then be created from that start date
3)  When cloning this template, you wouldn't have to calculate the
delta between the
template's date and the initial start date that you plan for the clone
of this template

Does anyone know of a way to do this?
  - I could keep this template in another directory or re-name it as
.TXT so that the agenda wouldn't pick up
the template's fake start dates, but this seems hacky.

Thanks
--Nate

             reply	other threads:[~2012-08-02 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 17:12 Nathan Neff [this message]
2012-08-03  7:25 ` Templates for cloning Bastien
2012-08-04  2:40   ` Sebastian Fischmeister
2012-08-06  1:35     ` Nathan Neff
2012-08-09  0:42       ` Sebastian Fischmeister

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='CAC=HedDJuf6AMXXXZKNbSKe9O6-3oWJeCQCc_z7wq1vOkSg-Bg@mail.gmail.com' \
    --to=nathan.neff@gmail.com \
    --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).