From: Greg Minshall <minshall@umich.edu>
To: "Berry, Charles" <ccberry@health.ucsd.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org-in-org
Date: Tue, 09 Mar 2021 06:37:01 +0300 [thread overview]
Message-ID: <1880300.1615261021@apollo2.minshall.org> (raw)
In-Reply-To: Your message of "Mon, 08 Mar 2021 20:33:59 +0000." <5A355522-851A-4ABD-9807-8CB1D7BE64E7@health.ucsd.edu>
Chuck,
> I admit to being baffled by this.
>
> If you have nested org src blocks and you recursively enter each org
> block using `org-edit-special' and execute the src blocks other than
> org lang, then exit with `org-edit-src-exit', when you complete this
> the org buffer will have nested src blocks and results with one or
> more comma escapes prepended to lines that start with `#+` or `*`.
ah.
> When you export this, you end up with a document that has the comma
> escapes reduced by one in those nested blocks. The appearance of these
> is not altogether pleasing to my eye.
yes, i see what you mean. though in a very limited pedagological
context, where you want to show the viewer of the exported document what
an org-in-org file looks like in an emacs .org buffer, i guess you might
want this.
for my use, your solution for org-in-org is exactly what i need.
cheers, Greg
next prev parent reply other threads:[~2021-03-09 3:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 14:24 org-in-org Greg Minshall
2021-02-23 19:46 ` org-in-org Berry, Charles via General discussions about Org-mode.
2021-03-07 16:14 ` org-in-org Greg Minshall
2021-03-07 22:26 ` org-in-org Berry, Charles via General discussions about Org-mode.
2021-03-08 7:44 ` org-in-org Greg Minshall
2021-03-08 20:33 ` org-in-org Berry, Charles via General discussions about Org-mode.
2021-03-09 3:37 ` Greg Minshall [this message]
2021-02-23 20:30 ` org-in-org Erik Iverson
2021-03-07 15:46 ` org-in-org Greg Minshall
2021-02-23 21:38 ` org-in-org Jeremie Juste
2021-03-07 16:06 ` org-in-org Greg Minshall
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=1880300.1615261021@apollo2.minshall.org \
--to=minshall@umich.edu \
--cc=ccberry@health.ucsd.edu \
--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).