From: Ihor Radchenko <yantar92@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>,
John Kitchin <jkitchin@andrew.cmu.edu>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: get the body of a heading up to the next subheading
Date: Thu, 14 May 2020 00:41:21 +0800 [thread overview]
Message-ID: <87lflvaitq.fsf@localhost> (raw)
In-Reply-To: <87eernu8bi.fsf@ericabrahamsen.net>
> I don't think there's anything built-in, no. I have needed this in
> various places, and did something similar to the above, except with a
> combination of `org-back-to-heading', `org-end-of-meta-data', then
> `outline-next-heading'.
Hmm. I just noticed a reference to built-in
org-agenda-get-some-entry-text in the function I sent earlier.
I do not see why it cannot be used outside agenda. Maybe something like
(let ((org-agenda-entry-text-cleanup-hook nil))
(org-agenda-get-some-entry-text (point-marker) #x40000000))
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> Thanks! Here is what I am currently using:
>>
>> (defun canvas-org-get-heading-body ()
>> "Return the body of the current heading up to the next heading."
>> (interactive)
>> (save-excursion
>> (unless (org-at-heading-p)
>> (org-previous-visible-heading 1))
>> (org-end-of-meta-data)
>> (buffer-substring (point)
>> (progn (re-search-forward org-heading-regexp nil 'mv)
>> (line-beginning-position)))))
>>
>> So far it gets what I want. I am pretty sure I have reinvented this,
>> maybe even from code I wrote before... I couldn't find my answer on SO
>> or my blog though.
>
> I don't think there's anything built-in, no. I have needed this in
> various places, and did something similar to the above, except with a
> combination of `org-back-to-heading', `org-end-of-meta-data', then
> `outline-next-heading'.
--
Ihor Radchenko,
PhD,
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
prev parent reply other threads:[~2020-05-13 16:53 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
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 [this message]
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=87lflvaitq.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=jkitchin@andrew.cmu.edu \
/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).