From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Release 6.28 Date: Thu, 2 Jul 2009 23:09:48 +0200 Message-ID: <1DE1D0DE-DABA-4492-8571-6EA8B3A887F7@gmail.com> References: <697A2093-E226-4AD6-B7DE-21A2DA8208A6@gmail.com> <7AC3F553-5E38-42A3-8761-EE44AE69D51B@gmail.com> Mime-Version: 1.0 (Apple Message framework v935.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MMTZW-0001tW-FU for emacs-orgmode@gnu.org; Thu, 02 Jul 2009 17:11:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MMTZQ-0001p7-V8 for emacs-orgmode@gnu.org; Thu, 02 Jul 2009 17:11:57 -0400 Received: from [199.232.76.173] (port=34095 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MMTZQ-0001oz-Ss for emacs-orgmode@gnu.org; Thu, 02 Jul 2009 17:11:52 -0400 Received: from mail-ew0-f208.google.com ([209.85.219.208]:62584) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MMTZQ-0002hM-Ja for emacs-orgmode@gnu.org; Thu, 02 Jul 2009 17:11:52 -0400 Received: by ewy4 with SMTP id 4so2448186ewy.42 for ; Thu, 02 Jul 2009 14:11:51 -0700 (PDT) In-Reply-To: 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: Christian Egli Cc: emacs-orgmode@gnu.org On Jul 1, 2009, at 12:26 PM, Christian Egli wrote: > > Hi all > > Carsten Dominik writes: > >> On Jul 1, 2009, at 9:20 AM, Ulf Stegemann wrote: >>> Carsten Dominik wrote: >>>> Bulk action >>>> ============ >>>> >>>> We can add more actions, if you convince me they make sense. >>> >>> IMHO setting scheduled (and maybe deadline) date would make sense. >> >> In what sense? Shifting all dates by the same amount, or setting >> them >> all to a fixed date? > > I usually display unscheduled TODO items in my agenda as well > (org-agenda-include-all-todo), so if I decide that I should work on > some > of them next week then a bulk action to schedule them might come in > handy. > > So one use case is to set a fixed scheduled date for a number of > TODOs. > In my case these are tasks that have not been scheduled yet. > > Another use case is when I decide that there will not be enough time > this week to complete all scheduled tasks. I want to move some of the > tasks to next week. This could be either a shift by 7 days or a > rescheduling to next monday (a fixed date). This should work now, I added "s" and "d" as bulk commands. Both commands will prompt for a date, and that date will be set for all entries. If you specify something like "++2d" at the prompt, all dates will be shifted by the same amount. - Carsten