emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: rjhorn@alum.mit.edu
Cc: Robert Horn <rjhorn@panix.com>, emacs-orgmode@gnu.org
Subject: Re: Update for habit documentation
Date: Thu, 14 Oct 2010 14:07:09 +0200	[thread overview]
Message-ID: <2ABF43F2-80AB-4F2D-8DCC-7F578D072F9C@gmail.com> (raw)
In-Reply-To: <4CB60DCA.4020102@alum.mit.edu>

Applied, thanks!

- Carsten

On Oct 13, 2010, at 9:51 PM, Robert Horn wrote:

> On 09/29/2010 12:07 PM, Carsten Dominik wrote:
>> Hi Robert,
>>
>> would you like to formulate a patch to org.texi?
>>
>
> This is my proposed patch. I hope I've done this right.
>
> *** org.texi	2010-10-06 09:06:20.000000000 -0400
> --- org.texi-original	2010-07-21 12:42:48.000000000 -0400
> ***************
> *** 3809,3818 ****
>  @item
>  The property @code{STYLE} is set to the value @code{habit}.
>  @item
> ! The TODO has a scheduled date, usually with a @code{.+} style repeat
> interval.
> ! A @code{++} style may be appropriate for habits with time  
> constraints,
> e.g.,
> ! must be done on weekends, or a @code{+} style for an unusual habit
> that can
> ! have a backlog, e.g., weekly reports.
>  @item
>  The TODO may also have minimum and maximum ranges specified by  
> using the
>  syntax @samp{.+2d/3d}, which says that you want to do the task at
> least every
> --- 3809,3815 ----
>  @item
>  The property @code{STYLE} is set to the value @code{habit}.
>  @item
> ! The TODO has a scheduled date, with a @code{.+} style repeat  
> interval.
>  @item
>  The TODO may also have minimum and maximum ranges specified by  
> using the
>  syntax @samp{.+2d/3d}, which says that you want to do the task at
> least every

- Carsten

      reply	other threads:[~2010-10-14 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 15:01 Update for habit documentation Robert Horn
2010-09-29 16:07 ` Carsten Dominik
2010-10-13 19:51   ` Robert Horn
2010-10-14 12:07     ` Carsten Dominik [this message]

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=2ABF43F2-80AB-4F2D-8DCC-7F578D072F9C@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rjhorn@alum.mit.edu \
    --cc=rjhorn@panix.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).