emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: "T.F. Torrey" <tftorrey@tftorrey.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-map-entries seems broken
Date: Wed, 13 Jan 2016 11:39:20 -0500	[thread overview]
Message-ID: <87k2ndfn7r.fsf@kyleam.com> (raw)
In-Reply-To: <87lh7trhpz.fsf@jack.tftorrey.com> (T. F. Torrey's message of "Wed, 13 Jan 2016 01:44:56 -0700")

Hello,

"T.F. Torrey" <tftorrey@tftorrey.com> writes:

> Hello,
>
> I have a function that uses org-map-entries to build a list of entries.
> It worked until recently.  Now, it fails with simple combinations.  For
> instance, 'LEVEL=1' matches what it should, and 'weblog' matches what it
> should, but 'LEVEL=1+weblog' does not match the intersecting set, or
> anything at all.  Did I miss a change in the syntax, or maybe did a
> recent refactoring introduce an error?  Does anyone else use this kind
> of matching and have it work?

Things seem to be working on my end.  Both release_8.3.3 and the
current master (23f31a9) are giving me the same results:

--8<---------------cut here---------------start------------->8---
#+begin_src elisp
  (org-map-entries
   (lambda () (substring-no-properties (org-get-heading t)))
   "LEVEL=1")
#+end_src

#+RESULTS:
| a | b |

#+begin_src elisp
  (org-map-entries
   (lambda () (substring-no-properties (org-get-heading t)))
   "atag")
#+end_src

#+RESULTS:
| aa | b | ba | bb |

#+begin_src elisp
  (org-map-entries
   (lambda () (substring-no-properties (org-get-heading t)))
   "LEVEL=1+atag")
#+end_src

#+RESULTS:
| b |

* a
** aa                                                                   :atag:
** ab
* b                                                                    :atag:
** ba
** bb
--8<---------------cut here---------------end--------------->8---

-- 
Kyle

  reply	other threads:[~2016-01-13 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13  8:44 Bug: org-map-entries seems broken T.F. Torrey
2016-01-13 16:39 ` Kyle Meyer [this message]
2016-01-17  3:06   ` T.F. Torrey

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=87k2ndfn7r.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tftorrey@tftorrey.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).