emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: agenda bulk actions
Date: Sat, 25 Aug 2012 00:55:39 -0700	[thread overview]
Message-ID: <877gsn76dg.fsf@ericabrahamsen.net> (raw)

I'm brushing up on org agenda commands, and have a question about bulk

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. 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.

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.

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.

Would this not be an improvement? Am I missing anything?


GNU Emacs (i686-pc-linux-gnu, GTK+ Version 2.24.11)
 of 2012-08-23 on pellet

             reply	other threads:[~2012-08-25  7:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-25  7:55 Eric Abrahamsen [this message]
2012-09-02 11:43 ` agenda bulk actions Bastien
2012-09-02 15:41   ` Eric Abrahamsen

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:

  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=877gsn76dg.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-orgmode@gnu.org \


* 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


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).