From: Carsten Dominik <email@example.com> To: Christian Egli <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Re: Release 6.28 Date: Thu, 2 Jul 2009 23:09:48 +0200 [thread overview] Message-ID: <1DE1D0DE-DABA-4492-8571-6EA8B3A887F7@gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Jul 1, 2009, at 12:26 PM, Christian Egli wrote: > > Hi all > > Carsten Dominik <email@example.com> writes: > >> On Jul 1, 2009, at 9:20 AM, Ulf Stegemann wrote: >>> Carsten Dominik <firstname.lastname@example.org> 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
next prev parent reply other threads:[~2009-07-02 21:11 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-25 7:10 Carsten Dominik 2009-06-25 7:14 ` Carsten Dominik 2009-06-25 13:05 ` Bastien 2009-06-25 13:19 ` Bastien 2009-06-25 13:58 ` Peter Frings 2009-06-25 16:16 ` Bastien 2009-06-25 17:34 ` Eric S Fraga, Eric S Fraga 2009-06-25 14:24 ` Carsten Dominik 2009-06-25 14:54 ` peter.frings 2009-06-25 14:57 ` Bernt Hansen 2009-06-25 15:34 ` Carsten Dominik 2009-06-25 16:15 ` Bastien 2009-06-25 19:34 ` Eric S Fraga 2009-06-25 17:00 ` Samuel Wales 2009-06-26 5:18 ` Carsten Dominik 2009-06-26 8:03 ` Carsten Dominik 2009-06-26 10:06 ` peter.frings 2009-06-26 14:05 ` Bernt Hansen 2009-06-26 14:14 ` Bastien 2009-06-26 10:59 ` Eric S Fraga, Eric S Fraga 2009-06-26 13:59 ` Carsten Dominik 2009-06-25 13:59 ` Sebastian Rose 2009-06-25 17:02 ` Eddward DeVilla 2009-06-25 17:10 ` Tom Tobin 2009-06-25 18:38 ` Xin Shi 2009-06-25 20:05 ` Matthew Lundin 2009-07-01 7:20 ` Ulf Stegemann 2009-07-01 9:47 ` Carsten Dominik 2009-07-01 10:26 ` Christian Egli 2009-07-01 11:17 ` Ulf Stegemann 2009-07-02 9:58 ` Carsten Dominik 2009-07-02 11:14 ` Ulf Stegemann 2009-07-02 11:33 ` Carsten Dominik 2009-07-02 21:09 ` Carsten Dominik [this message] 2009-07-03 12:32 ` Ulf Stegemann
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=1DE1D0DE-DABA-4492-8571-6EA8B3A887F7@gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Re: Release 6.28' \ /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
Code repositories for project(s) associated with this 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).