emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robert Goldman <rpgoldman@sift.info>
To: Matthew Lundin <mdl@imapmail.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Possible to get a subtree agenda view? --- possible bug?
Date: Sun, 14 Dec 2008 13:43:30 -0600	[thread overview]
Message-ID: <494561E2.7070807@sift.info> (raw)
In-Reply-To: <m2skors4jo.fsf@fastmail.fm>

Matthew Lundin wrote:
> Hi Robert,
> Robert Goldman <rpgoldman@sift.info> writes:
>> Matthew Lundin wrote:
>>> Hi Robert,
>> ....
>>>> Is there any existing way to do this, or should I start rooting around
>>>> in the code?
>>> 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
>>>         ))
>> Actually, I just tried this with a recent git pull, and when I try to
>> execute it, it crashes, with the following error:
> Sorry if I forgot to mention it in my first post, but I believe this
> custom command only works when the agenda is called from within an org
> buffer. As far as I understand it, since the tags tree command creates
> a sparse tree within an org buffer, it needs a particular org buffer
> to work with. 

If that is the case, isn't it incorrect to offer "tags-tree" as one of
the org-agenda custom commands?  Since it can't be safely invoked as
part of org-agenda?

One suggested possible solution:  Change tags-tree argument to (tags
tree <filename>), then do some kind of with-excursion to get into the
buffer for <filename> (in org mode).  But here we're running up against
my limited understanding of the tags tree.  Is tags-tree even really an
agenda command?  I.e., does it build a new agenda buffer that we can
use, or is it a way of viewing the current buffer?  I think the latter.
 If that is correct, it suggests ....

Alternate solution:  remove tags-tree from the set of org-agenda
commands.  tags-tree isn't really an agenda-building command, and should
not be treated as one.

Note also that this means that this doesn't work as a solution to my
problem, because it requires all of the car category items to appear in
a single org file, and ignores the org-agenda-files setting.  So, for
example, I can't have work-related in-car tasks in one org file and
personal chores that are in-car tasks in another.  :-(

  reply	other threads:[~2008-12-14 19:43 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 [this message]
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
2008-12-15  3:07         ` Matthew Lundin
2008-12-15  3:35           ` Robert Goldman
2008-12-15 10:50       ` Carsten Dominik

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=494561E2.7070807@sift.info \
    --to=rpgoldman@sift.info \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.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).