From: Robert Goldman <firstname.lastname@example.org>
To: Matthew Lundin <email@example.com>
Subject: Re: Possible to get a subtree agenda view?
Date: Sun, 14 Dec 2008 13:14:23 -0600 [thread overview]
Message-ID: <49455B0F.firstname.lastname@example.org> (raw)
Matthew Lundin wrote:
> Hi Robert,
> Robert Goldman <email@example.com> writes:
>> Matthew Lundin wrote:
>>> For a custom agenda command:
>>> (setq org-agenda-custom-commands
>>> '(("f" tags-tree "+car+TODO=\"TODO\""
>>> ((org-show-entry-below t)
>>> (org-show-hierarchy-above nil)))
>>> ;; other commands
>> In particular, the variable settings weren't near the agenda discussion,
>> and are not in the index. Question: would it be useful to add a
>> variable index to the info file? If it is, and there isn't someone more
>> texinfo competent than me to do it, I'll look into seeing how hard it
>> would be to do this.
>> Also, in the manual and code there's no real discussion of how the
>> settings part of the org-agenda-custom-commands is to be used. I mean,
>> it's clear that they are variable bindings, but there's no use case.
>> Would it be reasonable to modify your example above into an example to
>> be added to the texinfo file? I would be happy to have a whack if this
>> seems like a good idea.
> I'm guessing the best place for such a tutorial would be Worg (the
> org-mode wiki). http://orgmode.org/worg/
I think it would be appropriate to have a tutorial like this in Worg,
but not a replacement. If you look at the custom agenda commands
discussion in the manual, you will see that there is a discussion of how
most of the fields of custom command s-expression are to be used, but no
mention of the settings. I was just arguing that modifying the example
in the manual (or, possibly adding material from your example to it)
would be useful.
As an aside, I found the doc string somewhat confusing, as well. The
"settings A list of option settings, similar to that in a let form, so like
this: ((opt1 val1) (opt2 val2) ...). The values will be
evaluated at the moment of execution, so quote them when
needed." [apologies --- Thunderbird will no doubt make a hash of this]
I don't believe that there is any special notion of "option settings"
that this should be --- isn't this just a command that can be used to
bind arbitrary variables?
I will try to write up a proposed documentation patch and post it to the
list. Probably easier at this point to do that than to try to describe
what I /would/ do!
next prev parent reply other threads:[~2008-12-14 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 18:05 Possible to get a subtree agenda view? Robert Goldman
2008-12-13 21:29 ` Matthew Lundin
2008-12-13 22:35 ` Possible to get a subtree agenda view? --- possible bug? Robert Goldman
2008-12-14 5:34 ` Matthew Lundin
2008-12-14 19:43 ` Robert Goldman
2008-12-13 23:43 ` Possible to get a subtree agenda view? Robert Goldman
2008-12-14 13:46 ` Matthew Lundin
2008-12-14 19:14 ` Robert Goldman [this message]
2008-12-15 3:07 ` Matthew Lundin
2008-12-15 3:35 ` Robert Goldman
2008-12-15 10:50 ` Carsten Dominik
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 \
* 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).