From: Jeff Filipovits <jrfilipovits@gmail.com>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: emacs-orgmode@gnu.org
Subject: Re: Get the text of a node
Date: Wed, 23 Oct 2019 17:01:26 +0000 [thread overview]
Message-ID: <CAGE1zdnT981fVVKALeK76UV6nF1JhAkG2fYZzW8Mc+nZqNXGnw@mail.gmail.com> (raw)
In-Reply-To: <877e4vj0zf.fsf@fastmail.fm>
[-- Attachment #1: Type: text/plain, Size: 2194 bytes --]
Sometimes giving a bad answer inspires someone else to give a better one,
so here goes:
It seems like the best way to get the contents programatically is using
org-dp (https://github.com/tj64/org-dp). I don't see a way in org-element.
The data returned will include the property drawer of the heading. It does
not include subheadings.
I wrote a quick and ugly function to strip out the property drawer (it also
has to remove the properties list associated with the section element,
hence excluding :begin), and then returns a string.
(defun get-contents (data)
"DATA is the data returned by (org-dp-contents)"
(let ((contents)
(exclusions '(property-drawer :begin)))
(dolist (element (cdar data))
(unless (memq (car-safe element) exclusions)
(push element contents)))
(org-element-interpret-data (reverse contents))))
I am skeptical that this is a better way then the alternative you
described, but do not know. Hopefully someone else can assist.
On Wed, Oct 23, 2019 at 12:10 PM Joost Kremers <joostkremers@fastmail.fm>
wrote:
> Hi all,
>
> I was wondering if there's a way to programmatically get the text
> of a node in an Org buffer. Basically, I have a buffer that looks
> something like this:
>
> #+BEGIN_SRC org
> * Top header
> ** Subheader
> :PROPERTIES:
> :Custom_ID: some_id
> :END:
>
> Text starts here, possibly with additional subheaders
> #+END_SRC
>
> What I would like to extract is the text below "Subheader", but
> without the :PROPERTIES: block.
>
> I've looked at the org-element library, but I haven't been able to
> figure out how to use it to extract just the plain text.
>
> I use the :Custom_ID: property to find the relevant subheading and
> I know I can use (org-back-to-heading) to get point to the
> Subheader containing the relevant :PROPERTIES: block. Obviously, I
> could then narrow the buffer to the subheader, use a text search
> to move point past the line containing :END: and then extract the
> text from there until (point-max).
>
> I'm just wondering if this may break in unexpected circumstances
> and whether there's a better way.
>
> TIA
>
> Joost
>
>
>
> --
> Joost Kremers
> Life has its moments
>
>
[-- Attachment #2: Type: text/html, Size: 3048 bytes --]
next prev parent reply other threads:[~2019-10-23 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 8:54 Get the text of a node Joost Kremers
2019-10-23 17:01 ` Jeff Filipovits [this message]
2019-10-23 22:43 ` Sebastian Miele
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=CAGE1zdnT981fVVKALeK76UV6nF1JhAkG2fYZzW8Mc+nZqNXGnw@mail.gmail.com \
--to=jrfilipovits@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=joostkremers@fastmail.fm \
/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).