From: Ulf Stegemann <ulf-news@zeitform.de>
To: emacs-orgmode@gnu.org
Subject: Re: Release 6.28
Date: Thu, 02 Jul 2009 13:14:44 +0200 [thread overview]
Message-ID: <zf.upneiszmj4r.fsf@zeitform.de> (raw)
In-Reply-To: CB61443C-55DF-4D1D-BF80-4FCCCFC83C94@gmail.com
Carsten Dominik <carsten.dominik@gmail.com> wrote:
> On Jul 1, 2009, at 1:17 PM, Ulf Stegemann wrote:
>> Yes, both shifting by the same amount and setting a fixed date can be
>> useful. I usually re-schedule leftover todos by shifting them by one
>> or two working days to the future. So originally I had a bulk version of
>> `org-agenda-do-date-later' and friends in mind as opposed to
>> `org-agenda-schedule'. But the latter one would be useful to. Ideally,
>> S-left, C-cC-s et al. would trigger a bulk shift/bulk schedule whenever
>> there are marked agenda items.
>
> I am not so sure about this last point. I am not a
> fan of automatic bulk action if several items are selected.
>
> - these lists can become long, and selected entries might
> be off the screen
> - for this to make sense, selected entries should remain
> selected after action, increasing the danger of unwanted action
> - you might be in the process of selecting some entries, when you
> want to do a quick action on an individual entry you come across.
> But you cannot, because any action will act on all selected ones.
>
> So I do prefer a special command like "B" to introduce bulk action.
I undecided on this, too. Automagically working on marked entries should
they exists seems more natural to me but you are right more dangerous,
too. So I'm perfectly with you except that I'd say that marked entries
should be unmarked after the action. But anyway, triggering bulk actions
with a special command appears absolutely fine to me.
Ulf
next prev parent reply other threads:[~2009-07-02 11:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 7:10 Release 6.28 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 [this message]
2009-07-02 11:33 ` Carsten Dominik
2009-07-02 21:09 ` Carsten Dominik
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=zf.upneiszmj4r.fsf@zeitform.de \
--to=ulf-news@zeitform.de \
--cc=emacs-orgmode@gnu.org \
/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 public 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).