emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Leo Gaspard <orgmode@leo.gaspard.io>
To: emacs-orgmode@gnu.org
Subject: Re: [feature] Handle recurrence in <> and [] dates
Date: Tue, 06 Nov 2018 21:34:26 +0900	[thread overview]
Message-ID: <8736segzal.fsf@llwynog.ekleog.org> (raw)
In-Reply-To: <87tvldzzn8.fsf@llwynog.ekleog.org>

Hello all!

It's been ~2 weeks so I hope you'll forgive me bumping my post :)

Do you have an opinion about this idea?
Cheers,
  Leo

Leo Gaspard <orgmode@leo.gaspard.io> writes:

> Hello all!
>
> I have been using org-mode for a few days (switching over from
> todo.txt [1]), and for the time being my experience has been great!
>
> There is a single thing I found weird up to now: it seems that
> recurrence tags in <> and [] “tags” don't get bumped when a task is
> completed and has a recurrence set in its SCHEDULED or DEADLINE date.
>
> The reason I'd like this is because I have monthly bank statements,
> which come in the next month, and I'd like to store the bank statement's
> date in a [] “tag” so that I can easily know which statement I'm
> supposed to handle, even though this date is neither a SCHEDULED (as I
> don't have the statement yet at the date it's produced) nor a DEADLINE
> (for the same reason).
>
> What do you think about this?
>
> Anyway, thanks a lot for the great work!
>
> Cheers,
>   Leo
>
>
> [1] http://todotxt.org/

  reply	other threads:[~2018-11-06 12:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 16:58 [feature] Handle recurrence in <> and [] dates Leo Gaspard
2018-11-06 12:34 ` Leo Gaspard [this message]
2018-11-06 13:15   ` Julius Dittmar
2018-11-06 14:36     ` Leo Gaspard
2018-11-10 19:01       ` Nicolas Goaziou
2018-11-11  3:27         ` Leo Gaspard
2018-11-14 15:29         ` Marco Wahl
2018-11-17 15:35           ` Nicolas Goaziou
2018-11-17 19:46             ` Marco Wahl

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=8736segzal.fsf@llwynog.ekleog.org \
    --to=orgmode@leo.gaspard.io \
    --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).