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

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to find the headline matching a string
Date: Tue, 03 Jun 2014 22:21:11 +0200	[thread overview]
Message-ID: <87ioohpww8.fsf@gmail.com> (raw)
In-Reply-To: <877g4y723u.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 03 Jun 2014 17:51:17 +0800")

Hello,

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> I guess it shouldn't be too surprising -- the org element stuff is
> completely parsing the entire buffer on every pass. The other function
> probably boils down to passing a few targeted regexps over the buffer.
> I've sneakily cc'd Nicolas to see what he thinks. My guess is we could
> replace the call to org-element-parse-buffer with something that
> creates/accesses the cached version of the parse tree, and things would
> go much more swiftly.

I didn't look closely into the issue, but I think the main reason is
that Element parses headlines thoroughly, including all properties,
scheduled keywords, which is not, by default, the case for
`org-map-entries'.

For most use-cases, you don't need the parser for headlines, as their
grammar is context free. IOW, `org-element-parse-buffer' doesn't predate
`org-map-entries'.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2014-06-03 20:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31 15:07 How to find the headline matching a string Chris Poole
2014-05-31 15:27 ` Eric Abrahamsen
2014-05-31 16:51   ` Chris Poole
2014-05-31 17:00     ` Igor Sosa Mayor
2014-05-31 17:31       ` Chris Poole
2014-05-31 17:53         ` Igor Sosa Mayor
2014-05-31 20:14     ` Thorsten Jolitz
2014-06-01  4:05       ` Eric Abrahamsen
2014-06-03  9:05         ` Thorsten Jolitz
2014-06-03  9:51           ` Eric Abrahamsen
2014-06-03 20:21             ` Nicolas Goaziou [this message]
2014-06-04  1:36               ` Eric Abrahamsen
2014-06-04 11:27                 ` Thorsten Jolitz

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=87ioohpww8.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    /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).