From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: agenda bulk actions Date: Sun, 02 Sep 2012 13:43:10 +0200 Message-ID: <87pq641wc0.fsf@altern.org> References: <877gsn76dg.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34852) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T88d7-0002fv-Tg for emacs-orgmode@gnu.org; Sun, 02 Sep 2012 07:46:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T88d6-0001tq-Hd for emacs-orgmode@gnu.org; Sun, 02 Sep 2012 07:46:17 -0400 Received: from mail-wg0-f49.google.com ([74.125.82.49]:48773) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T88d6-0001kH-BM for emacs-orgmode@gnu.org; Sun, 02 Sep 2012 07:46:16 -0400 Received: by mail-wg0-f49.google.com with SMTP id dt14so2797351wgb.30 for ; Sun, 02 Sep 2012 04:46:16 -0700 (PDT) In-Reply-To: <877gsn76dg.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 25 Aug 2012 00:55:39 -0700") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Abrahamsen Cc: emacs-orgmode@gnu.org Hi Eric, Eric Abrahamsen writes: > It seems to me there's some odd overlap here: we've got 'k' bound to > `org-agenda-action', which is used for marking items and shifting their > dates to the date under point, or for capturing using the date under > point as a default. Then there's 'm' and 'B', which are used for marking > items and… doing everything/anything else. > > Having two different ways of marking agenda items and operating on them > seems odd to me. Yes, a merge was needed here. > In my (very subjective) opinion, it would be much nicer > to have a single set of functions for this. What I'm envisioning is: > > 1. Use only m/B for all marking and bulk actions. When we hit 's' or 'd' > for reschedule or re-deadline, use the date under point (if there is > one) as a default. This covers the 'k' functionality for scheduling > and deadlines. It is implemented now. > 2. Have the regular capture interface check org-context to see if point > is on an agenda date. If it is, use that as the default date for any > date fields. This covers the 'k' functionality for capture. `k' now calls `org-agenda-capture' in agendas, which does this. > 2(a). If the above is too intrusive, provide a single org agenda key > ('k' would now be free) that calls org-capture using date under > point as a default. You have `org-capture-use-agenda-date' which, when set to `t', will let M-x org-capture RET behave exactly like `k'. > Would this not be an improvement? Am I missing anything? Definitly not. Thanks for the suggestions! -- Bastien