emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: David Maus <dmaus@ictsoc.de>
Cc: Chao LU <loochao@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: How to do Properties search by define an agenda command
Date: Thu, 11 Nov 2010 20:51:58 -0500	[thread overview]
Message-ID: <8762w3z4u9.fsf@fastmail.fm> (raw)
In-Reply-To: <87mxphuj4d.wl%dmaus@ictsoc.de> (David Maus's message of "Wed, 10 Nov 2010 19:30:10 +0100")

David Maus <dmaus@ictsoc.de> writes:

> At Wed, 10 Nov 2010 02:59:58 -0500,
> Chao LU wrote:
>> I'm trying to figure out how  to do Properties search by define an agenda
>> command.
>>
>> Here is my item in org file:
>>
>> *** Franz Schwabl / Quantum Mechanics
>>     :PROPERTIES:
>>     :TITLE: Quantum Mechanics
>>     :AUTHOR: Franz Schwabl
>>     :CATEGORY: Quantum Mechanics
>>     :TAGS: Quantum Mechanics, Group Theory
>>     :KEYWORD: Quantum Mechanics, Perturbation, Second Quantization
>>     :LOCATION: iTune
>>     :END:
>
> IIRC the space character of a property value must be escaped (%20)
> because Org uses the plain space character to separate multiple values
> in a property.  So the drawer should look like:
>
>     :PROPERTIES:
>     :TITLE: Quantum%20Mechanics
>     :AUTHOR: Franz%20Schwabl
>     :CATEGORY: Quantum%20Mechanics
>     :TAGS: Quantum%20Mechanics Group%20Theory
>     :KEYWORD: Quantum%20Mechanics Perturbation Second%20Quantization
>     :LOCATION: iTune
>     :END:
>
> But now, sadly, that's all we've got.  The search engine can only
> search for equal strings (e.g. TITLE="Quantum%20Mechanics") or regular
> expression and it does not handle multivalue properties.

I don't believe this is the case. The following search works fine for me
with the OP's properties drawer:

C-c a m TITLE="Quantum Mechanics"

> Looks like to use the intended functionality someone has to patch Org
> mode's tag search to handle multivalue properties.

I don't believe the space in property values is meant to indicate
multiple values (i.e., in the same way that ":" separates tags). Here's
an example from the manual:

--8<---------------cut here---------------start------------->8---
     * CD collection
     ** Classic
     *** Goldberg Variations
         :PROPERTIES:
         :Title:     Goldberg Variations
         :Composer:  J.S. Bach
         :Artist:    Glen Gould
         :Publisher: Deutsche Grammophon
         :NDisks:    1
         :END:
--8<---------------cut here---------------end--------------->8---

That said, one can create ad hoc multivalue properties by using regexps
in property searches.

Best,
Matt

  reply	other threads:[~2010-11-12  1:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10  7:59 How to do Properties search by define an agenda command Chao LU
2010-11-10 18:30 ` David Maus
2010-11-12  1:51   ` Matt Lundin [this message]
2010-11-13  6:09     ` David Maus
2010-11-13 15:31       ` Matt Lundin
2010-11-12  1:39 ` Matt Lundin

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=8762w3z4u9.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=dmaus@ictsoc.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=loochao@gmail.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
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).