emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Better way to specify the latex documentclass of an exported file without changing my configuration?
Date: Wed, 26 Mar 2014 15:57:54 +0100	[thread overview]
Message-ID: <m2r45pypl9.fsf@polytechnique.org> (raw)
In-Reply-To: <87d2h9uk2b.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 26 Mar 2014 15:10:52 +0100")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> It is in a :noexport: section already. Here is a quick test.
>>
>> Exporting
>>
>> * Test :noexport:
>>
>> #+begin_src sh
>> echo "date 1" >> ~/tmp/results
>> echo `date` >> ~/tmp/results
>> #+end_src
>>
>> #+begin_src sh :exports results :results silent
>> echo "date 2" >> ~/tmp/results
>> echo `date` >> ~/tmp/results
>> #+end_src
>>
>> yields this "~/tmp/results" file:
>>
>> date 2 Wed Mar 26 14:46:08 CET 2014
>>
>> The behavior is identical if the ":noexport:" tag is absent.
>
> Then I think you can at least remove the ":results silent" part, can't
> you?

Yes, indeed. I'm too used to putting these blocks in parts that are
actually exported. Sorry for the confusion,

Alan

      reply	other threads:[~2014-03-26 15:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  8:37 Better way to specify the latex documentclass of an exported file without changing my configuration? Alan Schmitt
2014-03-26  9:24 ` Feng Shu
2014-03-26 12:38   ` Fabrice Niessen
2014-03-26 12:53     ` Alan Schmitt
2014-03-26 18:46       ` Thomas S. Dye
2014-03-26 22:03         ` Alan Schmitt
2014-03-26 12:47   ` Alan Schmitt
2014-03-26 23:26     ` Richard Lawrence
2014-03-26 13:21 ` Nicolas Goaziou
2014-03-26 13:54   ` Alan Schmitt
2014-03-26 14:10     ` Nicolas Goaziou
2014-03-26 14:57       ` Alan Schmitt [this message]

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=m2r45pypl9.fsf@polytechnique.org \
    --to=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.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).