From mboxrd@z Thu Jan 1 00:00:00 1970 From: Friedrich Delgado Friedrichs Subject: Timestamps only for workdays Date: Tue, 21 Oct 2008 15:35:48 +0200 Message-ID: <20081021133548.GA32196@taupan.ath.cx> Reply-To: friedel@nomaden.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KsHOv-0007FS-D6 for emacs-orgmode@gnu.org; Tue, 21 Oct 2008 09:35:57 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KsHOt-0007F4-0p for emacs-orgmode@gnu.org; Tue, 21 Oct 2008 09:35:56 -0400 Received: from [199.232.76.173] (port=33495 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KsHOs-0007F1-PC for emacs-orgmode@gnu.org; Tue, 21 Oct 2008 09:35:54 -0400 Received: from dudelab.org ([212.12.33.202]:20477 helo=mail.dudelab.org) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KsHOs-0000iJ-Bz for emacs-orgmode@gnu.org; Tue, 21 Oct 2008 09:35:54 -0400 Received: from abrasax.taupan.ath.cx (p5B10E801.dip.t-dialin.net [91.16.232.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Friedrich Delgado Friedrichs", Issuer "User CA" (verified OK)) by mail.dudelab.org (Postfix) with ESMTP id 23236228148 for ; Tue, 21 Oct 2008 15:34:49 +0200 (CEST) Content-Disposition: inline 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 Hiho! I'm using org with the same set of files both at work and at home (synchronized via svn at the moment). I have regular tasks that I do every day, but some only on workdays. I'd like to have a robust way to specify that a certain task should be executed Monday-Friday. When I tick it as DONE on Friday, the schedule should switch to the next Monday. I've tried specifying several timestamps with ++1w, each for a different day, but that is not robust. For some reason, org will always switch the first timestamp one week forward, in addition to the one for the current day. ( just +1w doesn't help either ) Is there a solution for this already? Otherwise I guess this is a feature request. :) Kind regards FDF --=20 Friedrich Delgado Friedrichs