From mboxrd@z Thu Jan 1 00:00:00 1970 From: Austin Frank Subject: FR: multiple or repeating active timestamps in agenda Date: Mon, 21 Jan 2008 16:20:42 -0500 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0783747397==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JH454-0004AJ-OW for emacs-orgmode@gnu.org; Mon, 21 Jan 2008 16:21:22 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JH451-00047B-H8 for emacs-orgmode@gnu.org; Mon, 21 Jan 2008 16:21:22 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JH451-000471-96 for emacs-orgmode@gnu.org; Mon, 21 Jan 2008 16:21:19 -0500 Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JH451-0000Qd-0B for emacs-orgmode@gnu.org; Mon, 21 Jan 2008 16:21:19 -0500 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JH44w-0004j6-4w for emacs-orgmode@gnu.org; Mon, 21 Jan 2008 21:21:14 +0000 Received: from colossus.cvs.rochester.edu ([128.151.80.181]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 21 Jan 2008 21:21:14 +0000 Received: from austin.frank by colossus.cvs.rochester.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 21 Jan 2008 21:21:14 +0000 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --===============0783747397== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" --=-=-= Content-Transfer-Encoding: quoted-printable Hello! I'm getting to the point of actually using org for organization (as opposed to using it for note taking and publishing and procrastination). Currently, when a repeated task is marked as done, it shows up again in the agenda on the date of the next occurrence of the task as long as the task is scheduled or has a deadline. I'd like to request two additions to this behavior. First, would it be possible to add this same feature for active timestamps that don't occur in a SCHEDULED or DEADLINE line? I follow the advice in the manual and don't use SCHEDULED for meetings, but I do have some recurring meetings. So, for the following entry: =2D-8<---------------cut here---------------start------------->8--- * Standing Appointments ** TODO Meeting with Mike <2008-01-23 Wed 10:00-11:30 +1w> =2D-8<---------------cut here---------------end--------------->8--- I'd like to be able to mark it as done every week, without needing it to be SCHEDULED or have a DEADLINE. Currently, the first time I mark it as done, all past and future repetitions are also marked as done. Second, for some events with only a few repetitions I create multiple active timestamps within one entry instead of using a repeating timestamp. So, for example, I have an entry like: =2D-8<---------------cut here---------------start------------->8--- * Standing Appointments ** TODO Swing III <2008-01-21 Mon 19:30-21:30> <2008-01-28 Mon 19:30-21:30> <2008-02-04 Mon 19:30-21:30> =2D-8<---------------cut here---------------end--------------->8--- Given that we can't combine repetition intervals with date ranges (or can we?), would it be possible to add a new behavior to deal with this case? When a TODO entry contains multiple time stamps, all of them would show up in the agenda as TODO items. Marking the item as done would use the same logic used for dealing with repeaters, and would continue to include the next active timestamp in the agenda as a TODO. In the past I have dealt with this second case by adding more structure to the task: =2D-8<---------------cut here---------------start------------->8--- * Standing Appointments ** Swing III *** TODO Week 1 <2008-01-21 Mon 19:30-21:30> *** TODO Week 2 <2008-01-28 Mon 19:30-21:30> *** TODO Week 3 <2008-02-04 Mon 19:30-21:30> =2D-8<---------------cut here---------------end--------------->8--- This gets the job done, but seems unnecessarily cluttered and redundant to me. Thanks for considering it, /au =2D-=20 Austin Frank http://aufrank.net GPG Public Key (D7398C2F): http://aufrank.net/personal.asc --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHlQywlHMl2/XbR4ERApGIAJ0ahozETGR1n9jNRQjPVL6gBWrpXgCfRSZ7 oN/e51UwqUuCf10nhP5IHQ8= =7xCP -----END PGP SIGNATURE----- --=-=-=-- --===============0783747397== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============0783747397==--