emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: nicholas.dokos@hp.com
Cc: Org Mode <emacs-orgmode@gnu.org>, rpgoldman@sift.info
Subject: Re: Bug in latex export tutorial on worg ?
Date: Mon, 09 May 2011 21:10:01 -1000	[thread overview]
Message-ID: <m1iptjghfa.fsf@tsdye.com> (raw)
In-Reply-To: <9389.1305006788@alphaville.dokosmarshall.org> (Nick Dokos's message of "Tue, 10 May 2011 01:53:08 -0400")

Nick Dokos <nicholas.dokos@hp.com> writes:

> Nick Dokos <nicholas.dokos@hp.com> wrote:
>
>> Robert Goldman <rpgoldman@sift.info> wrote:
>> 
>> > Ah.  I get it now.  But then surely the above IS a bug -- presumably
>> > it's not usual for a person to wish their latex export configuration to
>> > appear, in verbatim block, in their org-generated latex document!
>> > 
>> 
>> Perhaps not in most cases, but a tutorial has to do exactly that: how
>> else is it going to show the reader what needs to be done? Certainly
>> not by omitting the code that the reader is supposed to use.
>> 
>
> After Tom's reply, I went and looked at the example and now I get it
> too :-) Sorry for being dense before.
>
> Nick
>
>
Hi Nick,

Actually, your diagnosis was exactly right, as usual.  The "buggy" example
came from a document meant as a tutorial.

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

  reply	other threads:[~2011-05-10  7:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  2:41 Bug in latex export tutorial on worg ? Robert Goldman
2011-05-10  2:54 ` Nick Dokos
2011-05-10  2:58   ` Robert Goldman
2011-05-10  3:15     ` Thomas S. Dye
2011-05-10  4:22     ` Nick Dokos
2011-05-10  4:46       ` Robert Goldman
2011-05-10  5:06         ` Nick Dokos
2011-05-10  5:53           ` Nick Dokos
2011-05-10  7:10             ` Thomas S. Dye [this message]
2011-05-10  5:25         ` Thomas S. Dye
2011-05-10 13:07           ` Robert Goldman
2011-05-10 16:01             ` Thomas S. Dye

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=m1iptjghfa.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    --cc=rpgoldman@sift.info \
    /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).