From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Chris Malone <chris.m.malone@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Collapse LaTeX source before start of main document?
Date: Thu, 5 May 2011 10:37:13 -0700 [thread overview]
Message-ID: <20110505103713.0ec59a15@kuru.homelinux.net> (raw)
In-Reply-To: <BANLkTi=j=XVs5_9zgw+-OqRWu84pY4PYTA@mail.gmail.com>
Hello Chris,
Sorry for the delay, had to attend a meeting.
On Thu, 5 May 2011 11:37:41 -0400
Chris Malone <chris.m.malone@gmail.com> wrote:
> Hi Suvayu,
>
> Thanks for sharing your use case - I'm interested in a few more
> details:
>
> > For example for my appendix and bibliography I use the following:
> >
> > #+INCLUDE: thesis-appendix.org :minlevel 1
[...]
>
> Would this #+INCLUDE line come within the last chapter headline? In
> other words did you have something like
>
> #+INCLUDE: frontmatter.org
> * Chapter 1
> ....
> * Chapter 2
> ...
> * Last Chapter
> ....
> #+INCLUDE: thesis-appendix.org :minlevel 1
> .
> .
> .
> \bibliography{master}
>
> With this, it seems that all of the appendix/backmatter gets folded
> into the last chapter heading. That is sort of the way I'm thinking
> of working my thesis, but it seems sub-optimal.
>
Yes that is correct. It folds into the last chapter, and I too find this
sub-optimal. If there was a way to specify certain headlines were
"special" and needed to be exported according to the sub-tree
properties, that would be ideal. Although I haven't looked into it, I'm
afraid it would require some lisp intervention.
That said, I just found a possible workaround. If you put the appendix
and bibliography and friends under the Footnotes headline, it somewhat
replicates the behaviour I would like to have. Something like this:
* Footnotes
[fn:1] footnote 1
[fn:2] footnote 2
#+INCLUDE: thesis-appendix.org :minlevel 1
#+LaTeX: \backmatter
#+LaTeX: \newpage
#+LaTeX: \addcontentsline{toc}{chapter}{\bibname}
#+LaTeX: \bibliographystyle{plain}
#+LaTeX: \bibliography{master}
After my thesis defence I might actually get around to attempting to
deal with this in lisp. Would be a good learning excercise. :)
> Chris
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-05-05 17:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 15:36 Collapse LaTeX source before start of main document? Chris Malone
2011-05-04 16:18 ` Matt Lundin
2011-05-04 18:05 ` Chris Malone
2011-05-04 22:23 ` Matt Lundin
2012-09-27 9:07 ` Renier Marchand
2012-09-27 15:33 ` Nick Dokos
2014-06-06 17:03 ` Eric Schulte
2014-06-07 19:48 ` Eric Schulte
2011-05-04 22:25 ` Suvayu Ali
2011-05-05 14:23 ` Chris Malone
2011-05-05 14:46 ` Suvayu Ali
2011-05-05 15:37 ` Chris Malone
2011-05-05 17:37 ` Suvayu Ali [this message]
2011-05-05 17:45 ` chris.m.malone
2011-05-05 18:02 ` Suvayu Ali
2011-05-06 15:41 ` Eric S Fraga
2011-05-06 17:04 ` Suvayu Ali
2011-05-06 12:34 ` Matt Lundin
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=20110505103713.0ec59a15@kuru.homelinux.net \
--to=fatkasuvayu+linux@gmail.com \
--cc=chris.m.malone@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).