From: "Cook, Malcolm" <MEC@stowers.org>
To: "'emacs-orgmode@gnu.org'" <emacs-orgmode@gnu.org>
Subject: seeking good practices for writing about org using org
Date: Wed, 3 Aug 2016 23:50:45 +0000 [thread overview]
Message-ID: <e133f5cb010f4fe190168b3aa1a1abe2@exchsrv2.sgc.loc> (raw)
Hi,
I am seeking good practices for writing about org using , erhm, well, org itself. (doh!)
I'd use these practices, for example, when writing examples of using org, or lessons in using org, or bug reports about org.
I reached of ob-org thinking this is what it was for, and wrote the following
--------------------------------------- (beginning of example)
Here is simple org book structure with chapters and a table of
contents at the end:
#+BEGIN_SRC org :exports both :results value
* chapter one
Fa la la
* chapter two
La di di
* table of contents
#+TOC:
#+END_SRC
--------------------------------------- (end of example)
My dashed expectations were that when executed and exported, this would produce a block of the org source, appropriately quoted, followed be the RESULTS, being, well, the rendered org.
Are your expectations the same as mine?
What do YOU do in such cases?
Are there good practices for this?
Am I off by a level in my meta-thinking?
Thanks!
Malcolm Cook - Kansas City
next reply other threads:[~2016-08-03 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 23:50 Cook, Malcolm [this message]
2016-08-04 2:15 ` seeking good practices for writing about org using org Charles C. Berry
2016-08-04 2:47 ` Cook, Malcolm
2016-08-04 16:24 ` Charles C. Berry
2016-08-04 20:56 ` Cook, Malcolm
2016-08-05 3:05 ` Charles C. Berry
2016-08-04 2:54 ` Cook, Malcolm
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e133f5cb010f4fe190168b3aa1a1abe2@exchsrv2.sgc.loc \
--to=mec@stowers.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.