emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Troxel <gdt@ir.bbn.com>
To: emacs-orgmode@gnu.org
Subject: exporter bindings in agenda
Date: Thu, 24 Apr 2014 08:50:29 -0400	[thread overview]
Message-ID: <rmiha5ievsa.fsf@fnord.ir.bbn.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]


I use org relatively normally, with notes, TODO items, and appointments
(active timestamps), and way too many of them scheduled to be done on
any given day.  I export all agenda files to a combined ics file and
then stick it someplace I can subscribe to it from non-emacs calendaring
software.

To do this, I first invoke the agenda (because I want to see that too),
and then, because C-c C-e is not bound in the agenda view, pick a random
item and hit return, and then "C-c C-e c c" to export.

I realize there is C-x C-w in the agenda, but that does something else
-- only exporting the items in the current agenda view.

So, I'd like to suggest having the export key bindings work in the
agenda buffer.   The problem is that many of them do not make sense
because there is not a single org file associated with the agenda.

My proposal is that C-c C-e should behave similarly to when in an org
file, but choices that require an associated org file should be omitted.
Specifically, I think the following options make sense:
  c c (ical combined)
  c a (ical all)
  P x (publish - choose project)
  P a (publish - all projects

One could omit P, because publishing and agendas are disconnected,  But
I don't see the harm in it working if someone types it; it's not like
they are likely to have meant something else.

[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]

             reply	other threads:[~2014-04-25  1:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 12:50 Greg Troxel [this message]
2014-05-22 11:20 ` exporter bindings in agenda Bastien
2014-05-22 11:53   ` Greg Troxel
2014-05-22 15:08     ` Bastien

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=rmiha5ievsa.fsf@fnord.ir.bbn.com \
    --to=gdt@ir.bbn.com \
    --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).