From: Josiah Schwab <jschwab@gmail.com>
To: Nooreen Dabbish <nerd@temple.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Using #+INCLUDE for a .tex file
Date: Thu, 03 Mar 2016 14:55:32 -0800 [thread overview]
Message-ID: <87k2ljmasb.fsf@gmail.com> (raw)
In-Reply-To: <CAPx+V7YQxEDK9VxZ78tCwg=NeOQrf34gWdVpoGkx-LAq2LBQQg@mail.gmail.com>
Hello Nooreen,
> I am now resorting to
>
> #BEGIN_LATEX
> \include{file}
> #+END_LATEX
>
> But I am unhappy with this solution because I would like to generate the
> include line as the raw results of a code block.
I don't know anything about code block results, but would
@@latex:\include{file}@@
or
#+LATEX: \include{file}
be better?
http://orgmode.org/manual/Quoting-LaTeX-code.html#Quoting-LaTeX-code
Hope that (might) help,
Josiah
next prev parent reply other threads:[~2016-03-03 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 22:13 Using #+INCLUDE for a .tex file Nooreen Dabbish
2016-03-03 22:55 ` Josiah Schwab [this message]
2016-03-04 7:25 ` Eric S Fraga
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=87k2ljmasb.fsf@gmail.com \
--to=jschwab@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nerd@temple.edu \
/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).