emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>,
	org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: get the body of a heading up to the next subheading
Date: Tue, 12 May 2020 13:11:14 +0800	[thread overview]
Message-ID: <87ftc5agb1.fsf@localhost> (raw)
In-Reply-To: <CAJ51ETrkYLsKJ2UXr2toRK8QmOzJpx80R7EUaVqpwEpjXqc40Q@mail.gmail.com>

You may use something similar to org-quick-peek--get-entry-text from
org-quick-peek package (https://github.com/alphapapa/org-quick-peek):

(cl-defun org-quick-peek--get-entry-text (marker &key keep-drawers keep-planning)
  "Return Org entry text from node at MARKER.
If KEEP-DRAWERS is non-nil, drawers will be kept, otherwise
  ;; Modeled after `org-agenda-get-some-entry-text'
  (let (text)
    (with-current-buffer (marker-buffer marker)
      ;; Get raw entry text
       (goto-char marker)
       ;; Skip heading
       (end-of-line 1)
       ;; Get entry text
       (setq text (buffer-substring
                   (or (save-excursion (outline-next-heading) (point))
      (insert text)
      (unless keep-drawers
        (goto-char (point-min))
        (while (re-search-forward org-drawer-regexp nil t)
          ;; Remove drawers
          (delete-region (match-beginning 0)
                         (progn (re-search-forward
                                 "^[ \t]*:END:.*\n?" nil 'move)
      (unless keep-planning
        (goto-char (point-min))
        (while (re-search-forward org-planning-line-re nil t)
          ;; Remove planning line
      (setq text (buffer-substring (point-min) (point-max))))
    (-reduce-r #'funcall (reverse (cons text (cons #'identity org-quick-peek-filter-functions))))))


John Kitchin <jkitchin@andrew.cmu.edu> writes:

> Hi everyone,
> I am trying to get the body of a heading up to the next subheading. For
> example with this org file,
> * quiz one
> This is the description.
> Use emacs for this.
> ** question 1
> what is 40 + 2
> If the point is in the first heading, I want to run a function that would
> return the string "This is the description.\nUse emacs for this."
> I thought there was a simple way to do that, but so far it has eluded my
> google fu. Any hints?
> John
> -----------------------------------
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu

Ihor Radchenko,
Center for Advancing Materials Performance from the Nanoscale (CAMP-nano)
State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China
Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg

  parent reply	other threads:[~2020-05-12  5:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 23:04 get the body of a heading up to the next subheading John Kitchin
2020-05-12  1:03 ` briangpowell .
2020-05-12  5:11 ` Ihor Radchenko [this message]
2020-05-13 14:15   ` John Kitchin
2020-05-13 14:38     ` Ihor Radchenko
2020-05-13 14:49       ` John Kitchin
2020-05-22 14:41         ` Bastien
2020-05-13 16:08     ` Eric Abrahamsen
2020-05-13 16:41       ` Ihor Radchenko

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:

  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=87ftc5agb1.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \


* 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


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).