From: Matt Price <moptop99@gmail.com>
To: Thomas Plass <thunk2@arcor.de>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: property matching in org-agenda-custom-commands
Date: Fri, 5 Apr 2019 21:26:53 -0400 [thread overview]
Message-ID: <CAN_Dec9fwrpMsh4Gi0kKOc3hXhVUBRkVvHMPgTCdHsjJ5VgcXg@mail.gmail.com> (raw)
In-Reply-To: <23719.47035.820485.461489@AGAME7.local>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
Ah, I was being pretty stupid. Thanks to both Thomas and Nick.
Is it possible to specify "current buffer only" in the definition of a
shortcut, but still produce an agenda, rather than a sparse tree? I find
the agenda in some ways easier to navigate than the sparse tree.
Also (side note) I'm having trouble using the boolean "|" in the pattern
for the property value. I thought something like one of these would work,
but I'm having some trouble with it:
+GRADE={"0"|"Fail"}
or maybe
+GRADE={0|Fail}
etc.
Thansk as always,
Matt
On Fri, Apr 5, 2019 at 4:17 PM Thomas Plass <thunk2@arcor.de> wrote:
> Matt,
>
> Matt Price wrote at 13:31 on April 5, 2019:
> :
> : ("F" "Failing Students in Current Buffer Only" tags-tree "+GRADE=\"0\"")
> :
> : However, this seems to choke, and the agenda is not generated.
>
> Works as advertised (docstring'ed?), I think. The 'tags-tree creates
> a sparse tree, not an agenda. Plain 'tags does. If that's what
> you're after.
>
> ("F" "Failing Students in Current Buffer Only" tags "+GRADE=\"0\"")
>
> Thomas
>
[-- Attachment #2: Type: text/html, Size: 1759 bytes --]
next prev parent reply other threads:[~2019-04-06 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 17:31 property matching in org-agenda-custom-commands Matt Price
2019-04-05 18:39 ` Nick Dokos
2019-04-05 20:16 ` Thomas Plass
2019-04-06 1:26 ` Matt Price [this message]
2019-04-06 9:06 ` Thomas Plass
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=CAN_Dec9fwrpMsh4Gi0kKOc3hXhVUBRkVvHMPgTCdHsjJ5VgcXg@mail.gmail.com \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=thunk2@arcor.de \
/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).