emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Buffer positions from `org-element-map'?
Date: Wed, 28 Jan 2015 03:24:02 +0100	[thread overview]
Message-ID: <87pp9zskvx.fsf@gmx.us> (raw)
In-Reply-To: alpine.OSX.2.00.1501271726400.663@charles-berrys-macbook.local

Hi Charles,

"Charles C. Berry" <ccberry@ucsd.edu> writes:

> What I would like is to have the same values of :begin as would be
> obtained by placing the cursor on each inline src block and evaluating
> (org-element-context). As is evident below, :begin is sometimes a
> relative position.

OK

> Suggestions on how to get the buffer position or some other way to do
> in situ buffer modifications from `org-element-map' without
> interpreting a complete parse tree (which I expect requires more
> computation that doing selected `delete then insert' operations) are
> welcome.

Regexp and cl!

Note, if you want it do always do it on the whole file use
org-with-wide-buffer.  You might also want to wrap it in a
save-match-data.

--8<---------------cut here---------------start------------->8---
#+BEGIN_SRC emacs-lisp :results code
  (save-excursion
   (goto-char (point-min))
   (cl-loop while (search-forward-regexp org-babel-inline-src-block-regexp nil t)
            collect (list :begin (match-beginning 1)
                          :at-heading (org-at-heading-p))))
#+END_SRC

#+RESULTS:
#+BEGIN_SRC emacs-lisp
((:begin 424 :at-heading nil)
 (:begin 461 :at-heading t)
 (:begin 493 :at-heading nil))
#+END_SRC


src_emacs-lisp{"not in headline"}

* src_emacs-lisp{"in head line"}

src_emacs-lisp{"not in headline"}
--8<---------------cut here---------------end--------------->8---

Hope it helps,
Rasmus

-- 
Governments should be afraid of their people

  reply	other threads:[~2015-01-28  2:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28  1:48 Buffer positions from `org-element-map'? Charles C. Berry
2015-01-28  2:24 ` Rasmus [this message]
2015-01-28  7:32 ` Nicolas Goaziou

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=87pp9zskvx.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    /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).