From: "Cook, Malcolm" <MEC@stowers.org>
To: "'Charles C. Berry'" <ccberry@ucsd.edu>
Cc: "'emacs-orgmode@gnu.org'" <emacs-orgmode@gnu.org>
Subject: Re: seeking good practices for writing about org using org
Date: Thu, 4 Aug 2016 02:47:36 +0000 [thread overview]
Message-ID: <682129b907fb4b438f5571483c797797@exchsrv2.sgc.loc> (raw)
In-Reply-To: <alpine.OSX.2.20.1608031903450.989@charles-berrys-macbook.local>
[-- Attachment #1.1: Type: text/plain, Size: 2971 bytes --]
Thanks. Much closer. Still some issues. Mind taking another gander.... (hoping the attached jpeg of the webpage rendered comes through as an attachment)....
If my emacs buffer holds...
----------------------------------------------
#+BEGIN_SRC org :exports both :results value ascii
,* Acknowledgments
[[mailto:mywife@example.com][my wife]]
,* Chapter one
Fa la la ls
,* Chapter two
La di di
,* Finally, here is a table of contents!
,#+TOC:
#+END_SRC
----------------------------------------------
....Then exporting to html gives me a webpage with what I think are still a few issues:
* I would expect the 2nd line not to display as an emacs link text. I am trying to display the contents of the emacs buffer.
* There is not table of contents.
As in this screen shot.
Thanks for you TIPS!
> -----Original Message-----
> From: Charles C. Berry [mailto:ccberry@ucsd.edu]
> Sent: Wednesday, August 03, 2016 9:16 PM
> To: Cook, Malcolm <MEC@stowers.org>
> Cc: 'emacs-orgmode@gnu.org' <emacs-orgmode@gnu.org>
> Subject: Re: seeking good practices for writing about org using org
>
> On Wed, 3 Aug 2016, Cook, Malcolm wrote:
>
> > 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?
> >
>
> No. Run `M-x org-lint RET' and you will see that this is malformed. The
> org code needs to be escaped.
>
> > What do YOU do in such cases?
>
> Edit the src block in an edit buffer. You'll need to kill the contents of
> that src block first, then C-c ' to open the src edit buffer, then yank, then C-c
> '
> again. The resulting buffer will be properly escaped.
>
> See (info "(org) Literal examples"), especially footnote 4.
>
> --
>
> Then specify `:results replace' to override `:results silent' which
> `org-babel-default-header-args:org' sets.
>
> --
>
> Then the export should be what you expect.
>
> HTH,
>
> Chuck
[-- Attachment #1.2: Type: text/html, Size: 5353 bytes --]
[-- Attachment #2: Picture (Device Independent Bitmap) 1.jpg --]
[-- Type: image/jpeg, Size: 43993 bytes --]
next prev parent reply other threads:[~2016-08-04 2:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 23:50 seeking good practices for writing about org using org Cook, Malcolm
2016-08-04 2:15 ` Charles C. Berry
2016-08-04 2:47 ` Cook, Malcolm [this message]
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
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=682129b907fb4b438f5571483c797797@exchsrv2.sgc.loc \
--to=mec@stowers.org \
--cc=ccberry@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).