emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: York Zhao <gtdplatform@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Document of org-map-entries
Date: Fri, 14 Oct 2016 00:05:26 -0400	[thread overview]
Message-ID: <CAD3zm21SrjtchXbZVNUmua5g5-_AHHQCOBMGy=GDiE+5ssos-g@mail.gmail.com> (raw)
In-Reply-To: <8760ow9r8e.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]

@Nick:

Thanks for the explanation, it's very kind of you!

@John:

You are right, this actually works. However, this will also exclude the
trees
whose property value is empty, for example, the following tree will be
excluded,
which will not be excluded if "myproperty<>nil" syntax works:

* Tree
:PROPERTIES:
:myproperty:
:END:

But there's probably no point to have such empty property after all. So you
approach is acceptable. Thanks!

Regards,

York


On Thu, Oct 13, 2016 at 11:57 AM, Nick Dokos <ndokos@gmail.com> wrote:

> York Zhao <gtdplatform@gmail.com> writes:
>
> > Thank you very much Nick.
> >
> > (info "(org) Using the mapping API") was the first doc I read which has
> very little information on how
> > to use the "match" parameter.  (info "(org) Matching tags and
> properties") does have a lot more detail
> > though.
> >
>
> Understood - I like to give more complete information for two reasons:
>
> 1) I don't know what you have seen already, so maybe I can save an
>    exchange or two on the list by being more complete - and if you
>    have seen it already, no harm done.
>
> 2) Perhaps I'm fooling myself, but I like to think that somebody down
>    the line is going to have the same question, and if gmane ever
>    comes back :-), they might be able to search the list and find the
>    information that they need without having to send an email to the
>    list (or even if they do, somebody might be around who remembers
>    and can do the search and reply with "See this message").
>
> So no disparagement/offense meant at all, that is just my modus operandi.
>
> Regards,
> --
> Nick
>
>
>

[-- Attachment #2: Type: text/html, Size: 2349 bytes --]

      reply	other threads:[~2016-10-14  4:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13  4:16 Document of org-map-entries York Zhao
2016-10-13  4:46 ` Nick Dokos
2016-10-13  5:00   ` York Zhao
2016-10-13  5:25     ` York Zhao
2016-10-13 14:05       ` John Kitchin
2016-10-13 15:57     ` Nick Dokos
2016-10-14  4:05       ` York Zhao [this message]

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='CAD3zm21SrjtchXbZVNUmua5g5-_AHHQCOBMGy=GDiE+5ssos-g@mail.gmail.com' \
    --to=gtdplatform@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@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).