From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Troxel Subject: exporter bindings in agenda Date: Thu, 24 Apr 2014 08:50:29 -0400 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43020) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WdUpO-0004xL-1O for emacs-orgmode@gnu.org; Thu, 24 Apr 2014 21:22:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WdJ6k-0002d2-13 for emacs-orgmode@gnu.org; Thu, 24 Apr 2014 08:50:36 -0400 Received: from fnord.ir.bbn.com ([192.1.100.210]:59613) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WdJ6j-0002cw-Qi for emacs-orgmode@gnu.org; Thu, 24 Apr 2014 08:50:29 -0400 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: emacs-orgmode@gnu.org --=-=-= Content-Type: text/plain 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. --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlNZCJUACgkQ+vesoDJhHiUfDACeNpKUwNkE+sqHzIVjSpQcj1Bi w+gAn1+XbU6zAucJiUNdVFiGf6Z+XlQt =ohzR -----END PGP SIGNATURE----- --=-=-=--