From: "briangpowell ." <briangpowellms@gmail.com>
To: 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: Mon, 11 May 2020 21:03:15 -0400 [thread overview]
Message-ID: <CAFm0skE+ZH+008F9W6hoHfm-mq7LCPK=Ovj997Wf7qP-Hm3PkQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ51ETrkYLsKJ2UXr2toRK8QmOzJpx80R7EUaVqpwEpjXqc40Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]
Emacs was created to do such things--in fact the name E-macs is a terse
form of Editor-Macros {originally a derivative of TECO}
{There is a huge list of what Emacs should stand for--my fave is: Emacs
Makes All Computing Simple}
Now, what I'm suggesting is you make a macro, and store and reuse it--to
get you started, I suggest something like this
Cs*
Cn
C@
Cs**
Cx (
replace-string
Cqj
Return
\n
Return
Cx )
name-last-macro
Give it a name & save it & re-use it and/or EXTEND it later
On Mon, May 11, 2020 at 7:05 PM John Kitchin <jkitchin@andrew.cmu.edu>
wrote:
> 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
>
>
[-- Attachment #2: Type: text/html, Size: 2018 bytes --]
next prev parent reply other threads:[~2020-05-12 1:04 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 . [this message]
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
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='CAFm0skE+ZH+008F9W6hoHfm-mq7LCPK=Ovj997Wf7qP-Hm3PkQ@mail.gmail.com' \
--to=briangpowellms@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).