emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robert Goldman <rpgoldman@sift.info>
To: nicholas.dokos@hp.com
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Bug in latex export tutorial on worg ?
Date: Mon, 09 May 2011 23:46:12 -0500	[thread overview]
Message-ID: <4DC8C314.7020106@sift.info> (raw)
In-Reply-To: <8460.1305001352@alphaville.dokosmarshall.org>

On 5/9/11 May 9 -11:22 PM, Nick Dokos wrote:
> Robert Goldman <rpgoldman@sift.info> wrote:
> 
>> On 5/9/11 May 9 -9:54 PM, Nick Dokos wrote:
>>> Robert Goldman <rpgoldman@sift.info> wrote:
>>>
>>>> There is the following code block there:
>>>>
>>>> #+begin_src emacs-lisp :results silent
>>>>   (add-to-list 'org-export-latex-classes
>>>>           '("per-file-class"
>>>>              "\\documentclass{scrartcl}
>>>>              [NO-DEFAULT-PACKAGES]
>>>>              [EXTRA]"
>>>>              ("\\section{%s}" . "\\section*{%s}")
>>>>              ("\\subsection{%s}" . "\\subsection*{%s}")
>>>>              ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
>>>>              ("\\paragraph{%s}" . "\\paragraph*{%s}")
>>>>              ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
>>>> #+end_src
>>>>
>>>> Is this still correct?  Or should this be :exports none instead of
>>>> :results silent?
>>>>
>>>
>>> ``:results silent'' works for me and keeps the result from appearing in
>>> the org buffer. I don't think :exports can do that - it can only affect
>>> what's exported.
>>>
>>> Nick
>>
>> I must be doing something wrong then --- I had the :results silent and
>> found the source block in verbatim in my latex export file....  Changing
>> to :exports none made that go away for me.  Maybe that was a
>> coincidence.  I will have to investigate further, I guess.
>>
> 
> No, you are not doing anything wrong: the default :exports value is
> "code", so the code ends up in your export. ``:exports none'' keeps it
> (and any results) from being exported.
> 
> OTOH, try evaluating (C-c C-c) the code block, with and without
> ``:results silent''. There is a behavior difference and *that* difference
> is not affected by how you set :exports.
> 
> Nick

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!

Best,
Robert

  reply	other threads:[~2011-05-10  4:46 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 [this message]
2011-05-10  5:06         ` Nick Dokos
2011-05-10  5:53           ` Nick Dokos
2011-05-10  7:10             ` Thomas S. Dye
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=4DC8C314.7020106@sift.info \
    --to=rpgoldman@sift.info \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    /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).