From: "Thomas S. Dye" <tsd@tsdye.com>
To: Srinivas Pavani <sp_us@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-article & #+INCLUDE LaTex support
Date: Fri, 19 Nov 2010 08:43:56 -1000 [thread overview]
Message-ID: <62307F65-F7DC-434B-B327-31A718317DC8@tsdye.com> (raw)
In-Reply-To: <loom.20101119T185451-59@post.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2073 bytes --]
Aloha Srinivas,
On Nov 19, 2010, at 8:08 AM, Srinivas Pavani wrote:
> Tom,
>
> I have been trying to use the org-article LaTEX setup to get
> consistent look
> and feel across my documents.
>
> I found out that if you insert the following lines directly in a file
> (test.org), the desired output is produced. However if you insert
> the lines in
> an #+INCLUDE file, then the outcome is different. The settings of
> org-article
> are ignored.
>
>
> Test case 1:
>
> File: test.org
>
> #+OPTIONS: H:3
> #+LaTeX_CLASS: org-article
> #+LaTeX_CLASS_OPTIONS:
> [koma,letterpaper,captions=tableheading,utopia,11pt,listings-
> sv,microtype,paralist,colorlinks=true,urlcolor=blue,secnums]
> #+LATEX_HEADER: \usepackage[AUTO]{inputenc}
>
> * Sample Heading1
> ** Sample Heading2
> *** Sample Heading3
> Content goes here
>
> ----------------------------
>
> Test case 2:
> File: test.org
>
> #+include: boiler.org
> #+OPTIONS: H:3
>
> * Sample Heading1
> ** Sample Heading2
> *** Sample Heading3
>
> Content goes here
>
>
> File: boiler.org
> #+OPTIONS: H:2
> #+LaTeX_CLASS: org-article
> #+LaTeX_CLASS_OPTIONS:
> [koma,letterpaper,captions=tableheading,utopia,11pt,listings-
> sv,microtype,paralist,colorlinks=true,urlcolor=blue,secnums]
> #+LATEX_HEADER: \usepackage[AUTO]{inputenc}
>
> It seems that when files are included, the contents of the included
> file are
> not evaluated consistently. This seems like it is more of an issue
> with org-
> mode and interpreting include file contents.
>
> - Srinivas
Thanks for reporting this. I'm glad you're able to get the desired
output with org-article.
Org-article doesn't know anything about include files (perhaps it
should?), so I'm guessing along with you that this is an org-mode issue.
If I'm not mistaken, Eric Fraga reported this behavior as a bug
earlier today (http://lists.gnu.org/archive/html/emacs-orgmode/2010-11/msg00860.html
). I'll be interested in the discussion of this issue and any changes
that might be required for org-article to process include files
correctly.
All the best,
Tom
[-- Attachment #1.2: Type: text/html, Size: 2929 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-11-19 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 18:08 org-article & #+INCLUDE LaTex support Srinivas Pavani
2010-11-19 18:43 ` Thomas S. Dye [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=62307F65-F7DC-434B-B327-31A718317DC8@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=sp_us@yahoo.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).