emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@gnu.org>
To: Mike McLean <mike.mclean@pobox.com>
Cc: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Re: Strange Custom Agenda Problem
Date: Thu, 17 May 2012 07:54:32 +0200	[thread overview]
Message-ID: <87mx57qrmv.fsf@gnu.org> (raw)
In-Reply-To: <3CDE3A9D-C8AE-4DB4-B3AD-4BF888DA152F@pobox.com> (Mike McLean's message of "Wed, 16 May 2012 23:36:52 -0400")

Hi Mike,

Mike McLean <mike.mclean@pobox.com> writes:

> I have the following (amount other things) in my org-agenda-custom-commands:
>
> (setq org-agenda-custom-commands
>         '(("x" "test" tags-todo "+Outcome+LEVEL=4")))
>
> When I custom-command select “x”, I get no results. 

I tested with your `org-agenda-custom-commands' value and this

* Test
** Test1
*** Test2
**** TODO Do I see this?   :Outcome:

I correctly get :Outcome:.

This is with both the maint and master branches of the git repo.

> If I select the default, built-in lower case “m” agenda command and type
> +Outcome+LEVEL=4 I get a long list of results (as expected).

The "m" agenda command is for `tags', not `tags-todo'.

> Did something change recently in the agenda construction related to
> tags-todo?

This: http://orgmode.org/w/?p=org-mode.git;a=commit;h=c50f0c

Please help us reproduce the problem, perhaps by sharing some
of the impacted entries.

Thanks,

-- 
 Bastien

next prev parent reply	other threads:[~2012-05-17  5:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17  3:36 Strange Custom Agenda Problem Mike McLean
2012-05-17  5:54 ` Bastien [this message]
2012-05-17 12:56   ` Mike McLean
2012-05-17 13:04     ` Mike McLean
2012-05-17 17:25       ` Bastien
2012-05-21 16:06         ` Mike McLean
2012-05-23 10:17           ` Bastien
2012-05-23 11:22             ` Mike McLean
2012-05-23 12:32               ` Bastien
2012-05-22  4:18   ` Laurynas Biveinis
2012-05-23 10:17     ` Bastien
2012-05-23 15:36       ` Laurynas Biveinis

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=87mx57qrmv.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mike.mclean@pobox.com \
    /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

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).