From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josiah Schwab Subject: Re: Using #+INCLUDE for a .tex file Date: Thu, 03 Mar 2016 14:55:32 -0800 Message-ID: <87k2ljmasb.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42141) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1abc9h-000433-Pj for emacs-orgmode@gnu.org; Thu, 03 Mar 2016 17:55:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1abc9g-000448-PN for emacs-orgmode@gnu.org; Thu, 03 Mar 2016 17:55:37 -0500 Received: from mail-pa0-x22d.google.com ([2607:f8b0:400e:c03::22d]:36439) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1abc9g-00043w-I0 for emacs-orgmode@gnu.org; Thu, 03 Mar 2016 17:55:36 -0500 Received: by mail-pa0-x22d.google.com with SMTP id fi3so20766289pac.3 for ; Thu, 03 Mar 2016 14:55:36 -0800 (PST) In-reply-to: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nooreen Dabbish Cc: emacs-orgmode@gnu.org 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