From: Ihor Radchenko <yantar92@gmail.com>
To: Renato Pontefice <renato.pontefice@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Some question on How to handle date, recursive events
Date: Wed, 12 Oct 2022 17:39:19 +0800 [thread overview]
Message-ID: <87zge1gz3s.fsf@localhost> (raw)
In-Reply-To: <FB163357-1E3A-4AF4-839D-1A1C0607D026@gmail.com>
Renato Pontefice <renato.pontefice@gmail.com> writes:
> Hi,
> I’m building my own calendar. I try to check:
> 1 - retry a thing until it is not done
> 2 - recursive events (each week, every first Friday of month…)
>
>
> i.e.
> 1)
> ** TODO call Paul < 2022 10 05 10:30 +1d>
> In this example I’ve created an Agenda view that remember me to call Paul every day, at 10:30 each day until Paul answer me. Then I would set it as DONE.Today Paul has answers me, but if I try to set it as DONE (Shift - right arrow) it does not cycle to DONE state. I’ve thought that is the + 1d that block me to set as DONE. I’ve removed it and now it goes as DONE. But the entry still appear on next days as DONE. Why it does not erase it self from Agenda view? Is it possible? Or not?
1. You can run C-u -1 C-c C-t to inhibit the repeater (see org-todo
docstring; C-h f org-todo <RET>)
2. Check out org-agenda-skip-timestamp-if-done
> 2)
> Is the a way to set recursive events like “the firs Friday of the month” or each Tuesday of the month, not date-related (I mean: with +1 w I add the event the days x +7 days. Isn’t it?
See diary-style timestamps in https://orgmode.org/manual/Timestamps.html
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2022-10-12 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 8:21 Some question on How to handle date, recursive events Renato Pontefice
2022-10-12 9:39 ` Ihor Radchenko [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zge1gz3s.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=renato.pontefice@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.