From: Greg Troxel <gdt@ir.bbn.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: exporter bindings in agenda
Date: Thu, 22 May 2014 07:53:33 -0400 [thread overview]
Message-ID: <rmi1tvmrpvm.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87ppj6hxg6.fsf@bzg.ath.cx> (Bastien's message of "Thu, 22 May 2014 13:20:09 +0200")
[-- Attachment #1: Type: text/plain, Size: 2372 bytes --]
Bastien <bzg@gnu.org> writes:
> Greg Troxel <gdt@ir.bbn.com> writes:
>
>> 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
>
> I'm reluctant to do this because then C-c C-e would mean something
> very limited in agenda mode compared to what it means in Org mode.
It would be limited, but it would essentially be the subset that anyone
who understood might expect to work. I expected to be able to do the
ical combined export from agenda, because the combined ical export isn't
about any particular org file, and in the agenda I'm in org context.
Specifically, I did "C-C a a" to see the agenda, and then tried "C-c C-e c
c", to freshen my exported calendar daily. (I should just write a batch
file to do the calendar export after finding one of my files.)
> What I would find natural though is to have a "write to Org and
> export" mechanism: something that would write the current agenda view
> to an Org file and export this Org file.
That seems like a reasonable thing to have, but it seems entirely separate.
> I think C-c C-e would be good for this.
That would be ok, but the bindings should not overlap the org file
bindings. Or, the single file bindings could apply to the agenda, and
the combined to all. I think that would be intuitive to most.
I think what this comes down to is that within org users there are those
who have really internalized the rules/bindings and thus think of agenda
and org file as clearly different, and those who see them as subsets of
org and expect common behavior when it makes sense, realizing that some
things do and don't make sense given context. I realize many
keybindings are different, and have no problem with that. But I don't
see why I can't do the combined export, which is almost as appropriate
(org_context + 0/N) as in any one file (org_context + 1/N). It's
arguably more appropriate as the agenda is about the union of org files
rather than one.
But I can deal or change my own bindings, so the question is really
about what the ensemble of current and future users will find more
intuitive.
Thanks for thinking about this.
Greg
[-- Attachment #2: Type: application/pgp-signature, Size: 180 bytes --]
next prev parent reply other threads:[~2014-05-22 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 12:50 exporter bindings in agenda Greg Troxel
2014-05-22 11:20 ` Bastien
2014-05-22 11:53 ` Greg Troxel [this message]
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=rmi1tvmrpvm.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=bzg@gnu.org \
--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).