Hi Robert,
Robert Goldman <rpgold...@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.
Someone else please correct me if I'm wrong.
Re: the manual. I only mentioned it because I've found it to be such a
comprehensive and helpful source of information and I like to "spread
the word" about how good it is.
Best,
Matt
>
> Debugger entered--Lisp error: (error "Cannot execute org-mode agenda
> command on buffer in org-agenda-mode.")
> signal(error ("Cannot execute org-mode agenda command on buffer in
> org-agenda-mode."))
> ad-Orig-error("Cannot execute org-mode agenda command on buffer in
> %s." org-agenda-mode)
> apply(ad-Orig-error ("Cannot execute org-mode agenda command on buffer
> in %s." org-agenda-mode))
> error("Cannot execute org-mode agenda command on buffer in %s."
> org-agenda-mode)
> org-check-for-org-mode()
> byte-code(...)
> org-agenda(nil)
> call-interactively(org-agenda)
>
> Looks like something's being called here that is only callable in
> org-mode, not org-agenda-mode.
>
> Indeed, looking at org-agenda, I see:
>
> ((eq type 'tags-tree)
> (org-check-for-org-mode)
> (org-let lprops '(org-tags-sparse-tree current-prefix-arg
> match)))
>
> Aren't we always in org-agenda-mode at this point?
>
> I tried moving to a different buffer (in emacs-lisp mode) to invoke the
> same command, thinking it might be a problem specifically with invoking
> this custom agenda from inside org-agenda-mode, but then got the same
> error with emacs-lisp-mode instead of org-agenda-mode
>
> I have just this moment pulled an update from git, so I think this bug
> is current (unless it's some weird misconfiguration on my part).
>
> R
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
